Just tried to build a system using this stage1 and it fell over badly. Got as far as build binutils then tried to install gcc2.95-3 for some reason. gcc2.95 failed to build because I have athlon-mp for CFLAGS from the looks of it. USE="X gtk -gnome alsa kde mozilla mysql ssl xmms xv qtmt dvd motif acpi cdr -pcmcia -arts -cups -esd" CHOST="i686-pc-linux-gnu" CFLAGS="-march=athlon-mp -O3 -pipe" CXXFLAGS="${CFLAGS}" DISTDIR=/pub/portage/distfiles MAKEOPTS="-j4" rest of make.conf is commented out ake[3]: Entering directory `/var/tmp/portage/gcc-2.95.3-r7/work/gcc-2.95.3/gcc/intl' make[3]: Nothing to be done for `all'. make[3]: Leaving directory `/var/tmp/portage/gcc-2.95.3-r7/work/gcc-2.95.3/gcc/intl' ln -s ./../libiberty/obstack.c obstack.c stage1/xgcc -Bstage1/ -B/usr/i686-pc-linux-gnu/bin/ -c -DIN_GCC -O2 -march=athlon-mp -pipe -DHAVE_CONFIG_H -I. -I. -I./config -I./../include obstack.c stage1/xgcc -Bstage1/ -B/usr/i686-pc-linux-gnu/bin/ -c -DIN_GCC -O2 -march=athlon-mp -pipe -DHAVE_CONFIG_H -I. -I. -I./config -I./../include ./gengenrtl.c stage1/xgcc -Bstage1/ -B/usr/i686-pc-linux-gnu/bin/ -c -DIN_GCC -O2 -march=athlon-mp -pipe -DHAVE_CONFIG_H -I. -I. -I./config -I./../include version.c cc1: bad value (athlon-mp) for -march= switch cc1: bad value (athlon-mp) for -march= switch cc1: bad value (athlon-mp) for -march= switch make[2]: *** [version.o] Error 1 make[2]: *** Waiting for unfinished jobs.... make[2]: *** [obstack.o] Error 1 make[2]: *** [gencheck.o] Error 1 make[1]: *** [bootstrap-lean] Error 2 make[1]: Leaving directory `/var/tmp/portage/gcc-2.95.3-r7/work/gcc-2.95.3/gcc' make: *** [bootstrap-lean] Error 2 !!! ERROR: sys-devel/gcc-2.95.3-r7 failed. !!! Function src_compile, Line 108, Exitcode 2 !!! (no error message)
It seems to be picking up gcc2.95 because MYPROFILEDIR=/usr/portage/profiles/default-1.0
Actually I think this is the problem. /etc/make.profile/packages *=sys-devel/gcc-2.95.3-r7 *=sys-libs/glibc-2.2.5-r7
it is just a broken symlink for make.profile
Just another thing. The install docs say do env-update before emerge sync. This does not seem to work in practise, you have to do it after emerge sync.
fixed
