Configure fails checks with USE="libressl ssl" however builds fine with USE="libressl -ssl" Reproducible: Always Steps to Reproduce: 1. emerge openldap w/ +libressl +ssl 2. configure fails checks 3. change use for openldap +libressl -ssl 4. now able to compile. Actual Results: checking openssl/ssl.h usability... yes checking openssl/ssl.h presence... yes checking for openssl/ssl.h... yes checking for SSL_CTX_set_msg_callback in -lssl... no checking for ssl3_accept in -lssl... no configure: error: Could not locate TLS/SSL package Expected Results: Successful compilation. This is the only package that fails to build using libressl instead of openssl (with the libressl overlay).
Created attachment 481120 [details] emerge --info
I guess this would also fail with openssl[-sslv3].
That comes from a slight oversight in the ebuild (line 493 as of 2.4.45): local ssl_lib="no" if use ssl || ( ! use minimal && use samba ) ; then ssl_lib="openssl" use gnutls && ssl_lib="gnutls" fi myconf+=( --with-tls=${ssl_lib} ) Where the libressl useflag isn't checked. I'm not sure how this should be patched though. Should either of gnutls or libressl take precedence over the other? Should both be added to --with-tls? (Useflags for libressl and gnutls aren't mutually exclusive.)
Seing how gnutls takes precedence over openssl, I think it could do to make it so: ssl_lib="openssl" use libressl && ssl-lib="libressl" use gnutls && ssl_lib="gnutls"
The logic has been fixed in 2.4.45 and 2.4.44-r1. Both tested with all USE flags fine.
