--enable-quic --enable-opensslcoexist options are mutually exclusive about wolfssl

[kareem-wolfssl]

Hi @alexsn ,

This is an intentional error as our QUIC support depends extensively on our OpenSSL compatibility layer which is not compatible with OpenSSL coexistence. Are you able to share some information about your use case for linking wolf and OpenSSL into your application? Our OpenSSL compatibility layer supports many OpenSSL APIs and can be used in place of OpenSSL.

[alexsn]

Hey @kareem-wolfssl, thanks for the reply. The original issue I encountered was multiple function definitions when statically linking openssl with wolfssl.
I was able to get openssl / wolfssl to coexist without --enable-opensslcoexist by compiling wolfssl with NO_WOLFSSL_STUB and adding the following small change:

#if !defined(NETOS) && !defined(NO_WOLFSSL_STUB)
void ERR_load_SSL_strings(void)
{

}
#endif

Is this patch acceptable as I want ERR_load_SSL_strings to be removed in the presence of NO_WOLFSSL_STUB