If nss and ssl USE flags are enabled, the emerge fails in the configure step. If one or both of these are disabled, build continues without error. I experienced this error trying to compile both stable net-im/bitlbee-1.04 and ~x86 net-im/bitlbee-1.1 Reproducible: Always Steps to Reproduce: 1. Set USE flags to include both ssl and nss 2. Emerge net-im/bitlbee-1.0.4 or -1.1 Actual Results: Emerge has the following output: Calculating dependencies... done! >>> Emerging (1 of 1) net-im/bitlbee-1.1 to / * bitlbee-1.1dev.tar.gz RMD160 ;-) ... [ ok ] * bitlbee-1.1dev.tar.gz SHA1 ;-) ... [ ok ] * bitlbee-1.1dev.tar.gz SHA256 ;-) ... [ ok ] * bitlbee-1.1dev.tar.gz size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * checking bitlbee-1.1dev.tar.gz ;-) ... [ ok ] * Note: Support for all IM protocols are controlled by use flags. * Make sure you've enabled the flags you want. * >>> Unpacking source... >>> Unpacking bitlbee-1.1dev.tar.gz to /var/tmp/portage/net-im/bitlbee-1.1/work >>> Source unpacked. >>> Compiling source in /var/tmp/portage/net-im/bitlbee-1.1/work/bitlbee-1.1dev ... BitlBee configure ERROR: Could not find a suitable SSL library (GnuTLS, libnss or OpenSSL). Please note that this script doesn't have detection code for OpenSSL, so if you want to use that, you have to select it by hand. If you don't need SSL support, you can select the "bogus" SSL library. (--ssl=bogus) !!! ERROR: net-im/bitlbee-1.1 failed. Call stack: ebuild.sh, line 1614: Called dyn_compile ebuild.sh, line 971: Called qa_call 'src_compile' environment, line 3131: Called src_compile bitlbee-1.1.ebuild, line 146: Called die !!! econf failed !!! If you need support, post the topmost build error, and the call stack if relevant. !!! A complete build log is located at '/var/tmp/portage/net-im/bitlbee-1.1/temp/build.log'. Expected Results: emerge should have warned me if the USE flags are incompatible, or bitlbee configure should have been able to use both options (not sure which one is more "at fault" here). After disabling the nss flag, it worked fine. Thanks for your work on Gentoo.
*** This bug has been marked as a duplicate of bug 134202 ***
