Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 41095 - metamail won't start make, autoconf messed up?
Summary: metamail won't start make, autoconf messed up?
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Unspecified (show other bugs)
Hardware: x86 Linux
: High major (vote)
Assignee: Net-Mail Packages
URL:
Whiteboard:
Keywords:
: 48738 49533 (view as bug list)
Depends on:
Blocks: 47157 50138
  Show dependency tree
 
Reported: 2004-02-10 03:38 UTC by Arash Abedinzadeh
Modified: 2004-05-06 21:39 UTC (History)
6 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
Update configure.in as recommended in autoconf manual (mm-configure.in.diff,507 bytes, patch)
2004-04-25 21:36 UTC, Zach Bagnall
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Arash Abedinzadeh 2004-02-10 03:38:29 UTC
Hi, I really don't know if this is a bug or if I messed up something. Well, anyway...

The configure script starts normally, but then:

################################################

[..]
creating metamail/config.h
cd . && aclocal -I config
cd . && automake --foreign Makefile
cd . \
  && CONFIG_FILES=Makefile CONFIG_HEADERS= /bin/sh ./config.status
creating Makefile
cd . && autoconf
FATAL ERROR: Autoconf version 2.50 or higher is required for this script
make: *** [configure] Fehler 2

!!! ERROR: net-mail/metamail-2.7.45 failed.
!!! Function src_compile, Line 418, Exitcode 2
!!! emake failed

################################################

autoconf-2.59 is definetly installed. I also tried following:

################################################

WANT_AUTOCONF=2.5 emerge metamail
[..]
creating metamail/config.h
cd . && aclocal -I config
cd . && automake --foreign Makefile
cd . \
  && CONFIG_FILES=Makefile CONFIG_HEADERS= /bin/sh ./config.status
creating Makefile
cd . && autoconf
configure.in:350: 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] Fehler 1

!!! ERROR: net-mail/metamail-2.7.45 failed.
!!! Function src_compile, Line 418, Exitcode 2
!!! emake failed

###################################################

My "emerge info":

###################################################

Portage 2.0.50-r1 (default-x86-1.4, gcc-3.3.2, glibc-2.3.3_pre20040207-r0, 2.6.2-rc2)
=================================================================
System uname: 2.6.2-rc2 i686 AMD Athlon(tm) XP 1600+
Gentoo Base System version 1.4.3.13
distcc[22145] (dcc_trace_version) distcc 2.12.1 i686-pc-linux-gnu; built Jan 21 2004 21:48:42 [disabled]
ccache version 2.3 [enabled]
Autoconf: sys-devel/autoconf-2.59
Automake: sys-devel/automake-1.8.2
ACCEPT_KEYWORDS="x86 ~x86"
AUTOCLEAN="yes"
CFLAGS="-march=athlon-xp -mmmx -msse -m3dnow -mfpmath=sse -ffast-math -fomit-frame-pointer -O3 -pipe -funroll-loops -falign-functions=4"
CHOST="i686-pc-linux-gnu"
COMPILER="gcc3"
CONFIG_PROTECT="/etc /opt/glftpd/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.1/share/config /usr/kde/3.2/share/config /usr/kde/3/share/config /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d"
CXXFLAGS="-march=athlon-xp -mmmx -msse -m3dnow -mfpmath=sse -ffast-math -fomit-frame-pointer -O3 -pipe -funroll-loops -falign-functions=4"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs buildpkg ccache noclean sandbox userpriv usersandbox"
GENTOO_MIRRORS="ftp://sunsite.informatik.rwth-aachen.de/pub/Linux/gentoo"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage"
USE="3dnow X aalib acpi alsa apm arts avi berkdb cdr crypt directfb encode esd fbcon foomaticdb gdbm gif gnome gpm gtk gtk2 guile imlib java jpeg kde libg++ libwww mad mikmod mmx motif mpeg ncurses nls oggvorbis opengl oss pam pdflib perl png python qt quicktime readline ruby sdl slang spell sse ssl tcltk tcpd tetex truetype x86 xml2 xmms xosd xv zlib"

#######################################################

If you need more info, let me know.
Thanks in advance.

Arash

Reproducible: Always
Steps to Reproduce:
Comment 1 Arash Abedinzadeh 2004-02-10 03:40:14 UTC
Sorry for the de_DE@euro, forgot to switch to C.
Comment 2 SpanKY gentoo-dev 2004-02-11 18:20:53 UTC
can you try with libtool-1.5.2-r3 ?
Comment 3 Arash Abedinzadeh 2004-02-11 20:58:24 UTC
I did.
No changes, the error still occurs.
Comment 4 Patrick Borjesson 2004-02-12 09:08:50 UTC
I've got the same problem. 
Seems strange that the ebuild is marked stable when it doesn't even go through the autoconf-part. Or are we the only ones having this problem?
Comment 5 SpanKY gentoo-dev 2004-02-12 09:27:39 UTC
not really ... just because you're using an unstable set of autotools that cause stable packages to fail doesnt mean it's the stable packages' fault :P
Comment 6 Patrick Borjesson 2004-02-12 10:05:05 UTC
Well, this time it is since the manual page for autoconf (both 2.58 and 2.59) states that LIBOBJS in an forbidden token, which is what it complains about when trying to emerge the package with an autoconf-version of 2.5 or higher. And since the building of metamail requires >autoconf-2.5 it's pretty obvious that metamail is at fault even though it's an upstream issue.
Comment 7 revertex 2004-02-12 16:35:05 UTC
Autoconf-2.57-r1 reproduces a different error, but fail to compile too.
It complain about autoconf version, and it seems completely ignore the  "WANT_AUTOCONF=2.5" flag.
Autoconf-2.58 and autoconf-2.59 does the same errors as decribed by Arash.
Let me known if you need more info.


Comment 8 torgo 2004-02-13 09:28:42 UTC
very strange.  ran FEATURES="keeptemp keepwork" WANT_AUTOCONF="2.5" emerge metamail, and it failed.  Ran again, and it succeeded.  More research is in order...
Comment 9 cerement 2004-02-14 03:51:06 UTC
Had same problem: "FATAL ERROR: Autoconf version 2.50 or higher is required for this script"

Edited ebuild to read "make WANT_AUTOCONF=2.5 DESTDIR=${D} install || die" and got same error, reverted ebuild to original

tried "WANT_AUTOCONF=2.5 emerge metamail" and got the "error: do not use LIBOBJS directly, use AC_LIBOBJ (see section `AC_LIBOBJ vs LIBOBJS'"

tried "FEATURES="keeptemp keepwork" WANT_AUTOCONF="2.5" emerge metamail" and got success on first attempt
Comment 10 Daniel Pierce 2004-02-14 11:14:10 UTC
I ran "FEATURES="keeptemp keepwork" WANT_AUTOCONF="2.5" emerge metamail" and it failed with the "do not use LIBOBJS directly"...  Ran it again and it emerged ok.  Wierd.
Comment 11 Collins Richey 2004-02-14 22:20:13 UTC
I confirm that comment#10 is a good workaround; worked for me first attempt.  My environment is new system installed from scratch ~x86, nptl, 2.6.3_rc2, 2.6 headers, and udev.  emerge running in a terminal (aterm) under X (su -).
Comment 12 Terry 2004-02-15 18:44:48 UTC
comment 10 worked fine for me too, using sys-devel/autoconf-2.59-r1.
Comment 13 Arash Abedinzadeh 2004-02-15 19:11:40 UTC
comment 10 doesn't work for me.
And using autoconf-2.59-r1 produces the error message I described when using "WANT_AUTOCONF=2.5 emerge metamail". Seems that autoconf-2.59-r1 has fixed the wrapper as described in the autoconf changelog, but there problem remains:


configure.in:350: 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/metamail-2.7.45 failed.
!!! Function src_compile, Line 418, Exitcode 2
!!! emake failed
Comment 14 Patrick Borjesson 2004-02-17 14:49:21 UTC
I made a patch to configure.in which removes the offending code that autoconf complains about. This because of a section in autoconf's info about "AC_LIBOBJ vs LIBOBJS" (easy to find) which said that the code that it complains about is no longer neccesary in newer releases of autoconf. 
But when emerging with the patch it gets stuck somewhere running sed at 100% cpu. The last text displayed when doing it this way is the following:
...
checking for putenv... yes
configure: creating ./config.status
cd . \
  && CONFIG_FILES=Makefile CONFIG_HEADERS= /bin/sh ./config.status
config.status: creating Makefile

As the sed-portion of config.status is rather extensive I haven't been able to verify where sed gets stuck so I'm at a loss... Maybe some sed-guru can figure it out.
Comment 15 revertex 2004-02-17 22:17:51 UTC
thanks a lot, comment #10 works form me in the second try.
Comment 16 Alexander Würstlein 2004-02-18 03:52:03 UTC
For me, commenting out the offending lines (349-351) in configure.in worked without getting the said infinite loop from sed.
Comment 17 Paulo J. Matos 2004-02-18 09:17:48 UTC
Comment 10 worked for me. :D
Comment 18 Dane Elwell 2004-03-09 12:46:10 UTC
Comment 10 worked for me too, but I'm surprised this hasn't been fixed yet since it's in stable. Wonder if it's just certain people having trouble with it or whether it's a general thing.
Comment 19 Robin Munn 2004-03-16 06:56:14 UTC
I encountered the same problem, and comment #10 worked for me.
Comment 20 Sven Blumenstein (RETIRED) gentoo-dev 2004-03-20 08:36:39 UTC
Similar problem for me on Sparc, but the 'fix' in comment #10 worked for me too.

Raising severity -- there is only one version of metamail in the tree, and a fix should be included soon. 
Comment 21 Sven Blumenstein (RETIRED) gentoo-dev 2004-03-26 09:15:07 UTC
Any update on this?
Comment 22 Warp Zero (RETIRED) gentoo-dev 2004-03-28 18:12:36 UTC
This does not occur on x86 and was verified on PPC by liquidx, I would be happy to assist with ppc testing or whatever just ping me in #gentoo-dev, however i am on vacation currently and my internet access is spotty, but I'll be back by Thursday.
Comment 23 Sven Blumenstein (RETIRED) gentoo-dev 2004-03-29 02:07:55 UTC
Hmmm the first reporter got this on x86...
Comment 24 Jeremy Kitchen 2004-03-31 10:17:15 UTC
this bug is almost two months old, is anyone alive?  I can confirm this IS happening on x86, whomever said it wasn't must be doing something different.
Comment 25 Seemant Kulleen (RETIRED) gentoo-dev 2004-03-31 11:40:30 UTC
I just tried with autoconf-2.59-r3 and it worked for me -- I've actually never been able to repro this bug.  Would you believe I wish I could though.

what versions of autoconf, libtool and automake are y'all running? (where y'all == peeps experiencing this bug)
Comment 26 Jeremy Kitchen 2004-03-31 11:57:08 UTC
[ebuild   R   ] sys-devel/autoconf-2.58-r1   0 kB
[ebuild   R   ] sys-devel/libtool-1.4.3-r4   0 kB
[ebuild   R   ] sys-devel/automake-1.7.7   0 kB

steps to reproduce:
1) emerge metamail
2) wait a minute
3) cry.

actual output:
[snip]
creating bin/Makefile
creating metamail/config.h
cd . && aclocal -I config
cd . && automake --foreign Makefile
cd . \
  && CONFIG_FILES=Makefile CONFIG_HEADERS= /bin/sh ./config.status
creating Makefile
cd . && autoconf
configure.in:350: 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/metamail-2.7.45 failed.
!!! Function src_compile, Line 418, Exitcode 2
!!! emake failed

expected output:
>>> net-mail/metamail-2.7.45 merged.
Comment 27 Seemant Kulleen (RETIRED) gentoo-dev 2004-03-31 12:03:11 UTC
Calculating dependencies ...done!
[ebuild   R   ] sys-devel/autoconf-2.59-r3  
[ebuild   R   ] sys-devel/automake-1.8.3  
[ebuild   R   ] sys-devel/libtool-1.5.2-r5 

would you be willing to try those versions?
Comment 28 Piotr Kalinowski 2004-03-31 20:33:23 UTC
Still nothing...
Comment 29 David Oftedal 2004-04-03 11:26:11 UTC
configure.in:350: 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.
Comment 30 adam stokes 2004-04-06 13:58:40 UTC
  && CONFIG_FILES=Makefile CONFIG_HEADERS= /bin/sh ./config.status
creating Makefile
cd . && autoconf
configure.in:350: 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/metamail-2.7.45 failed.
!!! Function src_compile, Line 418, Exitcode 2
!!! emake failed


still get this error, have latest ~x86 libtool, autoconf, automake, used this command

FEATURES="keeptemp keework" WANT_AUTOCONF="2.5" emerge metamail

still failes
Comment 31 adam stokes 2004-04-06 17:15:29 UTC
eh ran #10 , and third times a charm! :(
Comment 32 Dewey 2004-04-13 06:24:23 UTC
Still broken. The keepwork/temp worked for me.

[ebuild  N    ] sys-devel/libtool-1.5.2-r5
[ebuild  N    ] sys-devel/autoconf-2.59-r3
[ebuild  N    ] sys-devel/automake-1.8.3

Please fix =)
Comment 33 Jason Wever (RETIRED) gentoo-dev 2004-04-13 07:43:38 UTC
Please do not remove people from the CC without asking them first.  There are reasons for some of us wanting to be on the CC.
Comment 34 Jeremy Kitchen 2004-04-13 08:44:45 UTC
Thanks for removing me from the CC.
Comment 35 Dane Elwell 2004-04-13 14:15:47 UTC
What's with the CC removal?
Comment 36 Collins Richey 2004-04-20 19:10:07 UTC
This bug is still alive and well for metamail-2.7.45, but the comment #10 workaround got me by the problem.
Comment 37 Gianluca Pacella 2004-04-25 03:21:58 UTC
Comment #10 worked also for me :)
Comment 38 Zach Bagnall 2004-04-25 21:36:42 UTC
Created attachment 30055 [details, diff]
Update configure.in as recommended in autoconf manual

Yeah #10 worked for me too.

Looking at the autoconf manual as suggested in the error output, it suggests a
replacement for the line used in metamail's configure.in.

If you replace line 350:

LTLIBOBJS=`echo X"$LIBOBJS"|[$Xsed -e "s,\.[^.]* ,.lo ,g;s,\.[^.]*$,.lo,"]`

with:

LTLIBOBJS=`echo X"$LIB@&t@OBJS" |
	   $Xsed -e 's,\.[[^.]]* ,.lo ,g;s,\.[[^.]]*$,.lo,'`

./configure will run without complaint.

Using:
*  sys-devel/autoconf
      Latest version available: 2.58-r1
      Latest version installed: 2.58-r1
/usr/portage/distfiles/mm2.7.tar.Z
/usr/portage/distfiles/metamail_2.7-45.diff.gz

diff on configure.in attached.
Comment 39 Jason Cox (RETIRED) gentoo-dev 2004-04-26 08:05:21 UTC
Comment 10 worked for me as well.
Comment 40 Florian Engelhardt 2004-04-30 08:22:26 UTC
Comment 10 worked for me as well :)
Comment 41 Brad Allen 2004-05-06 11:56:33 UTC
I didn't see comment #10 when I started, because I googled the
error first and found this in the home page of a program called
Trickle, which is similar to what comment #10 did and worked:


  URL:<"http://monkey.org/~marius/trickle/">:

quirks

  * note that on certain systems you may get the following error on "make":

       configure.in:220: 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_allo
             See the Autoconf documentation.
       make: *** [configure] Error 1

    this is easily circumvented by running make again.
                                   ^^^^^^^^^^^^^^^^^^

What I did was after the failure, do
 ebuild $(equery which metamail) compile install qmerge clean
which worked.

My system is mostly x86; only the kernel and headers in the base
system are above that.  There was only one version of metamail in
portage, so obviously trying other versions of metamail in portage
was a noop.  Re-emerging autoconf didn't fix the problem.  There
is no package named autotools.

autoconf strikes again.  autoconf has been starting to cause more
problems than it solves in recent years.  This is not Gentoo's fault.
However, I admit perhaps we don't know how much our dependency on
autoconf has grown (e.g., wonderful systems like Gentoo which might
have very different layouts from system to system) -- sort of like an
addiction.  What the C/Unix/Linux systems need is an effective project
to replace autoconf with something easier to program and more stable.
If autoconf were easier to program, we could fix it more often.  I've
tried many times to understand autoconf, and it is a complete mess.
Using scripts and macros is a really bad idea; autoconf should be
written in C.  The management of autoconf would then be that of
maintaining and distributing C code, which IMO would be a lot easier
than maintaining scripts and macros and properly integrating and
distributing the dependencies.  (The C code would probably be a very
obvious, straightforward, and simple implementation of a script
system, but one which doesn't have horrible, messy, and impossible to
understand syntax like autoconf scripts currently do.  No function
would be implemented in inferior scripts any more; parsing header
files and looking at library objects would be done either directly in
C or directly with program invocations from C.  There are probably
other autoconf reimplementation approaches to this problem which would
be better than the current situation.)  autoconf is so hard to program
that I can't tell whether or not the current bug is autoconf,
metamail, or some other program's fault.  (I never trust it until it
works, and even then not much.)
Comment 42 Steve Arnold archtester gentoo-dev 2004-05-06 21:02:59 UTC
*** Bug 48738 has been marked as a duplicate of this bug. ***
Comment 43 Steve Arnold archtester gentoo-dev 2004-05-06 21:28:37 UTC
*** Bug 49533 has been marked as a duplicate of this bug. ***
Comment 44 Steve Arnold archtester gentoo-dev 2004-05-06 21:39:32 UTC
Maybe I'm oversimplifying things, but an "autoreconf" seems to fix the problem and avoids the sed issue.  Is there some reason I shouldn't commit an update and close 
this bug?  Feel free to re-open this if I'm missing something crucial...