* Using GNU config files from /usr/share/libtool * Updating config.sub [ ok ] * Updating config.guess [ ok ] * Applying grub-0.95.20040823-splash.patch ... [ ok ] * Applying grub-0.95.20040823-warnings.patch ... [ ok ]>>> Source unpacked. /usr/share/aclocal/glib.m4:8: warning: underquoted definition of AM_PATH_GLIB run info '(automake)Extending aclocal' or see http://sources.redhat.com/automake/automake.html#Extending-aclocal configure.ac:19: version mismatch. This is Automake 1.7.9, configure.ac:19: but the definition used by this AM_INIT_AUTOMAKE configure.ac:19: comes from Automake 1.9.3. You should recreate configure.ac:19: aclocal.m4 with aclocal and run automake again. !!! ERROR: sys-boot/grub-0.95.20040823 failed. !!! Function src_compile, Line 61, Exitcode 1 !!! automake failed !!! If you need support, post the topmost build error, NOT this status message. this is due to the line in the ebuild of: WANT_AUTOMAKE=1.7 automake it should be: WANT_AUTOMAKE=1.7.9 automake or therre is some other more fundamental problem with automake-wrapper. Portage 2.0.51-r8 (selinux/2004.1/x86, gcc-hardened, glibc-2.3.4.20041102-r0, 2.6.5-gentoo-r1 i686) ================================================================= System uname: 2.6.5-gentoo-r1 i686 AMD Athlon (TM) MP Gentoo Base System version 1.6.7 Python: dev-lang/python-2.3.4 [2.3.4 (#1, Dec 3 2004, 09:59:31)] dev-lang/python: 2.3.4 sys-devel/autoconf: 2.59-r6, 2.13 sys-devel/automake: 1.9.3, 1.5, 1.8.5-r2, 1.6.3, 1.7.9, 1.4_p6 sys-devel/binutils: 2.15.90.0.1.1-r3, 2.15.92.0.2-r1 sys-devel/libtool: 1.5.2-r7 virtual/os-headers: 2.6.8.1-r1 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-O3 -march=athlon-mp -fomit-frame-pointer -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O3 -march=athlon-mp -fomit-frame-pointer -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig buildpkg ccache distlocks fixpackages sandbox sfperms strict" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="berkdb crypt gdbm java ncurses nls pam perl python readline selinux ssl x86 zlib"
The ebuild does autoconf || die "autoconf failed" aclocal || die "aclocal failed" WANT_AUTOMAKE=1.7 automake || die "automake failed" the call to aclocal autodetects the version, while the call to automake is wrongly forced to 1.7, while it should be 1.8. WANT_AUTOMAKE=1.7.9 is not recognized by the wrapper, so autodetection is used. The best thing to do is just to use the wrapper autodetection, maybe with something like autoreconf || die "autoreconf failed" (to also let autoconf/automake decide what commands to run). The strange thing is that it appears that the call to aclocal autodetected version 1.9 for you, while here it correctly runs aclocal-1.8. By the way: there's a more serious problem just below: has_pie && CC="${tc-getCC} `test_flag -fno-pic` `test_flag -nopie`" has_ssp && CC="${tc-getCC} `test_flag -fno-stack-protector`" should be: has_pie && CC="$(tc-getCC) `test_flag -fno-pic` `test_flag -nopie`" has_ssp && CC="$(tc-getCC) `test_flag -fno-stack-protector`"
... looking better at it, it seems the case (has_pie && has_ssp) is not handled correctly... and doing unset CFLAGS ... CFLAGS="${CFLAGS}" \ econf \ ... does not seem wise, too.
*** This bug has been marked as a duplicate of 73419 ***
