Scenario 1: USE flags: [ebuild U ] mail-client/muttng-20050809 [20050325] +berkdb +crypt +debug +gdbm +gnutls -gpgme -idn -imap -mbox -nls +nntp -pop -qdbm +sasl -slang +smtp +ssl Result: checking for getaddrinfo... yes configure: error: SASL2 support is only useful with POP or IMAP support !!! Please attach the config.log to your bug report: !!! /var/tmp/portage/muttng-20050809/work/muttng-20050809/config.log !!! ERROR: mail-client/muttng-20050809 failed. !!! Function econf, Line 485, Exitcode 0 !!! econf failed !!! If you need support, post the topmost build error, NOT this status message. Scenario 2: USE flags: [ebuild U ] mail-client/muttng-20050809 [20050325] +berkdb +crypt +debug +gdbm +gnutls -gpgme -idn -imap -mbox -nls +nntp -pop -qdbm -sasl* -slang +smtp +ssl Result: i686-pc-linux-gnu-gcc -Wall -pedantic -march=pentium4 -O2 -fprefetch-loop-arrays -fomit-frame-pointer -momit-leaf-frame-pointer -ftracer -fstack-protector -fstack-protector-all -pipe -I/usr/include -pthread -Wl,-O1 -Wl,--enable-new-dtags -Wl,--sort-common -o muttng patchlist.o alias.o ascii.o attach.o base64.o buffer.o browser.o buffy.o charset.o color.o compress.o crypt.o cryptglue.o commands.o complete.o compose.o copy.o curs_lib.o curs_main.o crypt-mod.o date.o edit.o editmsg.o enter.o flags.o filter.o from.o getdomain.o handler.o hash.o hcache.o hdrline.o headers.o help.o history.o hook.o init.o keymap.o lib.o main.o mbox.o mbyte.o md5c.o menu.o mh.o muttlib.o mutt_idna.o mx.o pager.o parse.o pattern.o postpone.o query.o recvattach.o recvcmd.o rfc822.o rfc1524.o rfc2047.o rfc2231.o score.o send.o sendlib.o sidebar.o signal.o sort.o state.o status.o system.o thread.o url.o utf8.o wcwidth.o xterm.o pgp.o pgpinvoke.o pgpkey.o pgplib.o gnupgparse.o pgpmicalg.o pgppacket.o crypt-mod-pgp-classic.o smime.o crypt-mod-smime-classic.o remailer.o resize.o account.o mutt_socket.o mutt_tunnel.o mutt_libesmtp.o regex.o -Lnntp -lnntp -Llib -lsane -lncursesw -pthread -L/usr/lib -lesmtp -lssl -lcrypto -ldl -L/usr/lib -lgdbm muttlib.o(.text+0xec): In function `mutt_adv_mktemp': : warning: the use of `mktemp' is dangerous, better use `mkstemp' mutt_libesmtp.o(.text+0x21a): In function `_mutt_libesmtp_auth_interact': : undefined reference to `mutt_get_password' collect2: ld returned 1 exit status distcc[25403] ERROR: compile (null) on localhost failed make[2]: *** [muttng] Error 1 make[2]: Leaving directory `/var/tmp/portage/muttng-20050809/work/muttng-20050809' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/muttng-20050809/work/muttng-20050809' make: *** [all] Error 2 !!! ERROR: mail-client/muttng-20050809 failed. !!! Function src_compile, Line 118, Exitcode 2 !!! emake failed (myconf= --disable-nls --disable-gpgme --disable-imap --disable-pop --without-sasl2 --enable-pgp --enable-nntp --enable-debug --with-libesmtp--without-idn --enable-compressed --sysconfdir=/etc/muttng --with-docdir=/usr/share/doc/muttng-20050809 --with-regex --disable-fcntl --enable-flock --with-mixmaster --enable-external-dotlock --enable-hcache --with-gdbm --without-qdbm --without-bdb --without-gnutls --without-ssl --with-curses --with-homespool=Maildir) !!! If you need support, post the topmost build error, NOT this status message. Reproducible: Always Steps to Reproduce: 1.Set USE flags 2.emerge muttng 3.
Fixed the first scenario. Do you understand what's happening in the second scenario? I don't yet.
This is just a guess: upstream problem. I suspect they also never tested using different configure combinations, themselves. I removed using libesmtp (-smtp), and it compiled without that error. One would need to look at the code to figure this out, which I was too lazy to do. I wonder how often they've compiled with POP and IMAP off? Guess: mutt_get_password is ifdefed out because of lack of POP support.
I pushed this bug upstream: http://developer.berlios.de/bugs/?func=detailbug&bug_id=4791&group_id=2853 Marking resolved for now, we'll just pick up the fix in a future snapshot.
Actually, the libesmtp support doesn't work at all, even when pop and imap are enabled. I've gone ahead and disabled it in the ebuild until it's repaired upstream.
