Hi! As mentioned above in the title, that happens when I build that version of mutt, although I have both USE-flags (imap and sasl) enabled. There go the build and the emerge --info. Thanks. Reproducible: Always
Created attachment 444722 [details] The build.log
Created attachment 444724 [details] The emerge --info
Same issue here. I have smtp, sasl, and imap enabled.
+1 Same issue. Mutt fails to build for me as well.
Created attachment 444912 [details] configure log
Thanks, would you please show me which use-flags you have enabled for mutt? I have now: mail-client/mutt-1.7.0 (berkdb crypt gpg imap mbox nls nntp sasl smime smtp ssl) So that's imap + sasl which works fine. I want to fix it, but don't understand why you get the error :/
The USE flags are in the build log. I'm pretty sure this is broken as a result of 0006-always-need-socket-for-getaddrinfo.patch. This removes the need_socket variable from some parts of configure.ac, but leaves behind a few references.
Aye, fixed for the next revbump.
please try with 1.7.0-r1
Not fixed at all yet. Tried with 1.7.10-r1 and I got the same error. BTW, the USE-flags I have enabled are: [U] mail-client/mutt Available versions: 1.5.23-r7 1.5.24-r2 (~)1.6.1-r1 (~)1.6.2 (~)1.7.0-r1 {berkdb crypt debug doc gdbm gnutls gpg idn imap kerberos libressl mbox nls nntp notmuch pop qdbm sasl selinux sidebar slang smime smtp ssl tokyocabinet} Installed versions: 1.6.2(16:12:43 10/07/16)(berkdb crypt gdbm gpg idn imap kerberos mbox nls sasl smtp ssl -debug -doc -gnutls -libressl -nntp -notmuch -pop -qdbm -selinux -sidebar -slang -smime -tokyocabinet) Homepage: http://www.mutt.org/ Description: A small but very powerful text-based mail client
May the error is in the configure script generated: 10529 # Check whether --with-sasl was given. 10530 if test "${with_sasl+set}" = set; then : 10531 withval=$with_sasl; 10532 if test "$with_sasl" != "no" 10533 then 10534 if test "$need_socket" != "yes" 10535 then 10536 as_fn_error $? "SASL support is only useful with POP or IMAP support" "$LINENO" 5 10537 fi
right, for some reason the right patch didn't end up in -r1. Checking it out Right Now(tm).
Created attachment 444956 [details, diff] replacement patch Here's a much simpler version of that patch; instead of trying to erase needs_socket from existence (and failing), just initialize it to "yes". However, it does break the other patch series (features-extra, gentoo).
http://marc.info/?l=mutt-dev&m=147299006108716&w=2 -r2 is going in now.
Built and working fine. Thank you. I hope it doesn't break other stuff.
it won't as I more or less restored the original behaviour now :)