Bug 22787 – mutt-1.5.4-r1 -make fails

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Wim Uyttebroek 2003-06-13 15:14:58 UTC]

my USE flags for mutt: [ebuild    U ] net-mail/mutt-1.5.4-r1 [1.5.4] +ssl +nls +slang -cjk 
+crypt -imap +mbox 
 
mutt-1.5.4.ebuild worked, but r1 gives a make error. 
 

Reproducible: Always
Steps to Reproduce:
1.
2.
3.
Actual Results:  
MAKE ERROR: 
creating po/Makefile 
cd . && aclocal-1.4 -I m4 
cd . && automake-1.4 --foreign --include-deps Makefile 
cd . && autoconf 
configure.in:343: error: do not use LIBOBJS directly, use AC_LIBOBJ (see section `AC_LIBOBJ 
vs LIBOBJS' 
      If this token and others are legitimate, please use m4_pattern_allow. 
      See the Autoconf documentation. 
make: *** [configure] Error 1 
 
!!! ERROR: net-mail/mutt-1.5.4-r1 failed. 
!!! Function src_compile, Line 82, Exitcode 2 
!!! make failed (myconf=--enable-nls --with-ssl                         --disable-imap --enable-pgp 
--with-slang --with-maildir=/var/spool/mail)

[Comment 1 Richard Garand 2003-06-24 19:53:14 UTC]

Same error with the following flags: 
 
[ebuild    U ] net-mail/mutt-1.5.4-r1 [1.5.4] +ssl +nls +slang -cjk +crypt -imap -mbox 
 
It's interesting that it runs autoconf after configuring it - unless they use some build 
process I've never heard of, this shouldn't happen. The Makefile probably has a 
rule to regenerate configure, and one of the files it depends on is newer; touching 
everything in the directory (I added 'touch *' before the make command) takes care 
of it. 
 
This doesn't look like a permanent problem; Makefile.in is 7 minutes newer than 
configure with this tarball, so it will probably go away with the next release. 

[Comment 2 Arnaud Launay 2003-06-25 15:27:52 UTC]

unset WANT_AUTOCONF_2_5, then you'll have no problem with the compilation of mutt.

[Comment 3 Wim Uyttebroek 2003-06-25 16:09:35 UTC]

>unset WANT_AUTOCONF_2_5 
This solved the problem for me
Is this going to be added to the ebuild ?

thanx

[Comment 4 Peter Johanson (RETIRED) 2003-07-07 09:37:47 UTC]

This has been commited. Please sync and test. Report back sucess/failures.

[Comment 5 Wim Uyttebroek 2003-07-08 03:35:42 UTC]

yes, it works now (without manually unsetting WANT_AUTOCONF_2_5)

thx

[Comment 6 Arnaud Launay 2003-12-07 16:21:18 UTC]

ChangeLog:  unset WANT_AUTOMAKE_2_5 to fix compilation. bug #22787
mutt-1.5.4-r1.ebuild:   unset WANT_AUTOMAKE_2_5
mutt-1.5.5.1.ebuild:    unset WANT_AUTOMAKE_2_5

Errrm... It's WANT_AUTOCONF_2_5, not MAKE...

[Comment 7 Ahmad Twaijry 2003-12-13 06:48:10 UTC]

Hi

I still can't compile mutt after rsync: (I have unset WANT_AUTOMAKE_2_5)

creating po/Makefile
cd . && aclocal-1.4 -I m4
cd . && automake-1.4 --foreign --include-deps Makefile
cd . && autoconf
configure.in:343: error: do not use LIBOBJS directly, use AC_LIBOBJ (see section `AC_LIBOBJ vs LIBOBJS'
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.
make: *** [configure] Error 1
 
!!! ERROR: net-mail/mutt-1.5.4-r1 failed.
!!! Function src_compile, Line 84, Exitcode 2
!!! make failed (myconf=--enable-nls --with-ssl                         --enable-imap --enable-pgp --with-slang --with-homespool=Maildir)

[Comment 8 Arnaud Launay 2003-12-13 06:59:52 UTC]

unset WANT_AUTOCONF_2_5, not autoMAKE.

[Comment 9 Aron Griffis (RETIRED) 2004-02-11 12:49:07 UTC]

fixed to use WANT_AUTOCONF, thanks

[Comment 10 Ascaride 2004-02-18 12:14:56 UTC]

I experienced this bug although if the ebuild contains "unset ANT_AUTOCONF_2_5".

Since autoconf don't use anymore WANT_AUTOCONF_2_5 I think it is needed to add somewhere in the ebuild also an "export WANT_AUTOCONF=2.1" (I did it manually   and it worked).

[Comment 11 Donnie Berkholz (RETIRED) 2004-02-22 11:43:12 UTC]

I'm definitely still hitting this error, and adding the 'export WANT_AUTOCONF=2.1' fixed it.

[Comment 12 Allen Parker 2004-02-23 04:41:27 UTC]

*bump* -- this bug is still alive

[Comment 13 Richard Garand 2004-02-23 11:08:21 UTC]

Might I remind the ebuild maintainers that, as my earlier comment points out, touching all the files in the root directory of the package prior to compilation will eliminate the inappropriate use of autoconf? Hopefully the next mutt release won't be packaged like this...