net-im/bitlbee-1.0.3 configure script fails when compiling with the "nss" use flag because it can't find the library. # -- Session Log -- # [1038] # emerge bitlbee Calculating dependencies... done! >>> Emerging (1 of 1) net-im/bitlbee-1.0.3 to / >>> checking ebuild checksums ;-) >>> checking auxfile checksums ;-) >>> checking miscfile checksums ;-) >>> checking bitlbee-1.0.3.tar.gz ;-) * 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.0.3.tar.gz to /var/tmp/portage/bitlbee-1.0.3/work * Applying bitlbee-1.0.3-xinetd.patch ... [ ok ] * Applying bitlbee-gentoohack.patch ... [ ok ] >>> Source unpacked. >>> Compiling source in /var/tmp/portage/bitlbee-1.0.3/work/bitlbee-1.0.3 ... BitlBee configure ERROR: Could not find a suitable SSL library (GnuTLS, libnss or OpenSSL). This is necessary for MSN and full Jabber support. To continue, install a suitable SSL library or disable MSN support (--msn=0). If you want Jabber without SSL support you can try --ssl=bogus. !!! ERROR: net-im/bitlbee-1.0.3 failed. Call stack: ebuild.sh, line 1545: Called dyn_compile ebuild.sh, line 940: Called src_compile bitlbee-1.0.3.ebuild, line 96: Called die !!! econf failed !!! If you need support, post the topmost build error, and the call stack if relevant. # -- End Session Log -- # I can reproduce the bug from the unpacked sources directory using `./configure --ssl=nss' Why is NSS preferred over GNUTLS or OpenSSL? I have the three of them installed, and the three USE flags are up, but still the ebuild chooses nss. It compiles fine with any of the latter. Here's the relevant section of the ebuild: # setup ssl use flags use ssl && use gnutls && myconf="${myconf} --ssl=gnutls" use ssl && use nss && myconf="${myconf} --ssl=nss" # <-- reason? use ssl && use !gnutls && use !nss && myconf="${myconf} --ssl=openssl" Thanks.
Created attachment 95519 [details] emerge --info
*** This bug has been marked as a duplicate of 134202 ***