When emerge -u world, portage begins to emerge sys-devel/automake-1.9.4. It then fails. Here's the Output: bash-2.05b# emerge -u world Calculating world dependencies ...done! >>> emerge (1 of 9) sys-devel/automake-1.9.4 to / >>> md5 src_uri ;-) automake-1.9.4.tar.bz2 >>> Unpacking source... >>> Unpacking automake-1.9.4.tar.bz2 to /var/tmp/portage/automake-1.9.4/work * Applying automake-1.9.3-infopage-namechange.patch ... [ ok ] * Using GNU config files from /usr/share/libtool * Updating lib/config.sub [ ok ] * Updating lib/config.guess [ ok ] >>> Source unpacked. * econf: updating automake-1.9.4/lib/config.guess with /usr/share/gnuconfig/config.guess * econf: updating automake-1.9.4/lib/config.sub with /usr/share/gnuconfig/config.sub ./configure --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib configure: WARNING: If you wanted to set the --build type, don't use --host. If a cross compiler is detected then cross compile mode will be used. checking build system type... i686-pc-linux-gnu checking for a BSD-compatible install... /bin/install -c checking whether build environment is sane... yes checking for gawk... gawk checking whether make sets $(MAKE)... yes checking for i686-pc-linux-gnu-strip... i686-pc-linux-gnu-strip checking for perl... /usr/bin/perl checking for tex... no checking whether autoconf is installed... no configure: error: Autoconf 2.58 or better is required. Please make sure it is installed and in your PATH. !!! Please attach the config.log to your bug report: !!! /var/tmp/portage/automake-1.9.4/work/automake-1.9.4/config.log !!! ERROR: sys-devel/automake-1.9.4 failed. !!! Function econf, Line 485, Exitcode 0 !!! econf failed !!! If you need support, post the topmost build error, NOT this status message. --------------------------------------- Here's the versions of autoconf I have installed: * sys-devel/autoconf : [ I] 2.13 (2.1) [ ] 2.59-r5 (2.5) [ I] 2.59-r6 (2.5) Here's the versions of automake I have installed: * sys-devel/automake : [ I] 1.4_p6 (1.4) [ I] 1.5 (1.5) [ I] 1.6.3 (1.6) [ ] 1.7.9-r1 (1.7) [ ] 1.8.5-r1 (1.5) [ ] 1.8.5-r3 (1.8) [ ] 1.9.4 (1.9)
Created attachment 50135 [details] /var/tmp/portage/automake-1.9.4/work/automake-1.9.4/config.log
***NOTE*** After looking at the log, it appeared that I was missing /usr/bin/autoconf. To resolve this issue, I: "cp /usr/bin/autoconf-2.59 /usr/bin/autoconf" which then allowed automake to compile. The question remains, how did autoconf go missing? Is this something portage did? I didn't remove it myself...
Maybe it's better to re-emerge autoconf-wrapper, at least this doesn't by-pass portage Similar problem in Bug #78814 (We will have this problem again and again, until we have figured out, what's deleting /usr/bin/autoconf)
I did find on the web an instance where something similar was happening, and the solution was to run: emerge -av automake-wrapper I did try this and it didn't fix the problem.
...sorry, I misread your comment...I did NOT try to re-emerge autoconf-wrapper ...only automake-wrapper
on another note.....I removed the /usr/bin/autoconf that I copied from /usr/bin/autoconf-2.59 and re-emerged autoconf-wrapper. I then re-emerged automake and it compiled with no problem.
That's the wrong way to fix it. /usr/bin/autoconf is supposed to be a symlink to a wrapper script that chooses the executable to use. The same wrapper is used for automake as well. Here's the right way. ln -s /usr/lib/misc/am-wrapper.sh /usr/bin/autoconf ln -s /usr/lib/misc/am-wrapper.sh /usr/bin/automake Now your problems should be fixed.
i rev bumped the wrappers so everyone would automagically get them re-emerged
