An attempt to bootstrap prefix portage on x86-linux failed. The failure occurs when emerging automake-1.10.1 for the last time, after having done `emerge --sync'. The failure printout complains on autoconf. It seems that a previous version of autoconf (2.61-r01.1) was usable, and that the current version (2.62) causes the failure. Here is text from the console log: >>> Emerging (24 of 87) sys-devel/automake-1.10.1 to / [ ... text deleted ... ] checking whether autoconf is installed... yes checking whether autoconf works... no configure: error: The installed version of autoconf does not work. Please check config.log for error messages before this one. !!! Please attach the following file when seeking support: !!! /local/scratch/portage/sys-devel/automake-1.10.1/work/automake-1.10.1/config.log * ERROR: sys-devel/automake-1.10.1 failed: * econf failed * * Call stack: * ebuild.sh: 49: <call src_compile> * environment:2086: <call econf '--docdir=/local/tmp/nightly/2008-04-11/usr/share/doc/automake-1.10.1'> * ebuild.sh: 526: die "econf failed" * * If you need support, post the topmost build error, and the call stack if relevant. * build log: '/local/scratch/portage/sys-devel/automake-1.10.1/temp/build.log' * ebuild environment: '/local/scratch/portage/sys-devel/automake-1.10.1/temp/environment' * S: '/local/scratch/portage/sys-devel/automake-1.10.1/work/automake-1.10.1'
Thanks. I'll mask it. I could forsee this coming. I want stable keywords for @system just to make bootstrapping less risky ...
masked
