Host system: SUSE Linux Enterprise Desktop 10 (i586), version = 10, patchlevel = 1, with minor undocumented modifications for corporate deployment. Procedure: http://www.gentoo.org/proj/en/gentoo-alt/prefix/bootstrap-linux.xml, December 1, 2007 version. Bootstrapping prefix portage fails when trying to emerge coreutils. The console output contains this: * Running autoconf ... [ !! ] * Failed Running autoconf ! * * Include in your bugreport the contents of: * * /tmp/local/g2/var/tmp/portage/sys-apps/coreutils-6.9-r1/temp/autoconf-27000.out and the .out file contains configure.ac:255: warning: AM_INTL_SUBDIR is m4_require'd but not m4_defun'd m4/gettext.m4:362: AM_GNU_GETTEXT is expanded from... configure.ac:255: the top level configure:52584: error: possibly undefined macro: AM_INTL_SUBDIR If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation.
(In reply to comment #0) > configure.ac:255: warning: AM_INTL_SUBDIR is m4_require'd but not m4_defun'd > m4/gettext.m4:362: AM_GNU_GETTEXT is expanded from... > configure.ac:255: the top level > configure:52584: error: possibly undefined macro: AM_INTL_SUBDIR > If this token and others are legitimate, please use m4_pattern_allow. > See the Autoconf documentation. Rabbe, You need to emerge autoconf-2.6* before trying coreutils. I found the fix by googling and came across an interesting post [1]. @grobian,haubi: You may want to update your docs/scripts for this bug. Hope that helps! =) [1]: http://osdir.com/ml/gnu.m4.patches/2006-11/msg00014.html
maybe we should lower the coreutils version we bootstrap there instead, haubi?
I tried prepending the line that emerges coreutils like this, env WANT_AUTOCONF=2.1 emerge ... but alas, now the emerge instead fails with /tmp/local/g2/var/tmp/portage/sys-apps/coreutils-6.9-r1/temp/aclocal-24399.out containing ***** aclocal ***** ac-wrapper: Autoconf 2.13 doesn't contain autom4te. Either unset WANT_AUTOCONF or don't execute anything that would use autom4te. aclocal-1.10: autom4te failed with exit status: 1
(In reply to comment #3) > I tried prepending the line that emerges coreutils like this, > > env WANT_AUTOCONF=2.1 emerge ... > > but alas, now the emerge instead fails with > /tmp/local/g2/var/tmp/portage/sys-apps/coreutils-6.9-r1/temp/aclocal-24399.out > containing > > ***** aclocal ***** > > ac-wrapper: Autoconf 2.13 doesn't contain autom4te. > Either unset WANT_AUTOCONF or don't execute anything > that would use autom4te. > aclocal-1.10: autom4te failed with exit status: 1 > @Rabbe: did you try what I suggested?
Hmm, no. But I must ask, do you mean that I should do emerge --oneshot --nodeps "=autoconf-2.6*" a second time, just before emerging coreutils? The webpage procedure [1] emerges autoconf-2.6* in step 1.9. I'll give it a shot, the machine is idling anyway right now. 1. <http://www.gentoo.org/proj/en/gentoo-alt/prefix/bootstrap-linux.xml>, December 1, 2007 version
Good news, the workaround worked! That is, insert an extra emerge --oneshot --nodeps "=sys-devel/autoconf-2.6*" immediately before emerge --oneshot --nodeps sys-apps/coreutils .. my bootstrapping is now well into the `emerge -e system' part.
autoconf-2.6 is now reemerged after m4, such that it actually works for coreutils. Thanks!
