Message-ID: <7a019859-7884-f278-2463-b07e9ee4e747@...1227...> Date: Thu, 1 Sep 2022 14:39:55 +0200 MIME-Version: 1.0 Content-Language: en-GB References: <20200429145132.28424-1-juliusz@...2525...> <41fef456-3ced-7cb3-7888-46a3522080b2@...2181...> <196ab7ef-4a2f-dc82-45a7-59295b5c36e7@...2525...> From: Arne Schwabe In-Reply-To: <196ab7ef-4a2f-dc82-45a7-59295b5c36e7@...2525...> Subject: Re: [Openvpn-devel] [PATCH] Support for wolfSSL in OpenVPN List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8"; format="flowed" Content-Transfer-Encoding: 8bit To: Juliusz Sosinowicz , Antonio Quartulli , openvpn-devel@lists.sourceforge.net >> (*)(const X509_NAME * const*, const X509_NAME * const*) {aka int >> (*)(const struct WOLFSSL_X509_NAME * const*, const struct >> WOLFSSL_X509_NAME * const*)} >> In file included from /usr/local/include/wolfssl/openssl/ssl.h:35, >>                   from ssl_openssl.h:32, >>                   from ssl_backend.h:36, >>                   from ssl_openssl.c:44: >> /usr/local/include/wolfssl/ssl.h:3534:47: note: expected >> ‘wolf_sk_compare_cb’ {aka ‘int (*)(const void * const*, const void * >> const*)’} but argument is of type ‘int (*)(const X509_NAME * const*, >> const X509_NAME * const*)’ {aka ‘int (*)(const struct WOLFSSL_X509_NAME >> * const*, const struct WOLFSSL_X509_NAME * const*)’} >>   3534 | WOLFSSL_API WOLF_STACK_OF(WOLFSSL_X509_NAME)* >> wolfSSL_sk_X509_NAME_new( >>        | >> ^~~~~~~~~~~~~~~~~~~~~~~~ > To make wolfSSL_sk_X509_NAME_new more universal we accept a function > with void* parameters. This will unfortunately generate a warning when > compiling with wolfSSL but won't affect functionality. This issue is still present and still breaks compiling with -Werror . Are there any plans to address this? Arne