If pound-2.3.2 or pound-2.4.5 is build with USE="static", then the configure process fails with: configure: *** Checking for libraries *** checking for dlopen in -ldl... yes checking for socket in -lsocket... no checking for hstrerror in -lresolv... yes checking for BIO_new in -lcrypto... yes checking for SSL_CTX_new in -lssl... no Missing OpenSSL (-lssl) - aborted ... whether USE="ssl" or USE="-ssl". Is USE="static" intended to be able to be enabled or disabled on a per-package basis? If not, shouldn't it be masked in the same way that USE="hardened" is... or otherwise, is this simply a quirk of the pound build process?
yes, USE="static" is intended to be enabled or disabled on a per-package basis. the failure here seems to be, that openssl does not provide a static version of libssl. of course, pound should not check for this, when USE="-ssl".... i'll be looking into this. thanks for the report
hhm. as turning of ssl doesnt work anymore the ssl useflag has been removed. as openssl doesnt install static libs anymore the static use flag was removed. sorry for the inconvinience. thanks for the report. kind regards Thilo
