[gentoo-dev] GCC3.1 bootstrap fails

[Prashanth Aditya Susarla]

Hello,
	I tried to bootstrap with the default-1.0-gcc3 profile at the
outset. The exact details are as follows:-
1.) I used the gentoo-1.1a-ix86.iso image to create my bootable CD
2.) Instead of using the stage-1 tbz2 file on this CD, I separately
downloaded the stage-1 build image from the 1.2 release and used that
instead
3.) As soon as I did the emerge rsync, I switched profiles and edited
make.conf. The optimization flags which I used are very simple - 
-march=i686 -O3 -fomit-frame-pointer
I also edited the packages file to unmask versions of binutils >= 2.12
4.) Executing bootstrap.sh compiled baselayout, gettext, binutils,
gcc-3.1-r5 and glibc-2.2.5-r3 without any hitches.
5.) As soon as glibc was merged and the bootstrap was going to remerge
everything again, gzip failed with a broken pipe and most binaries started
segfaulting (notably emerge and even ls!).

>From the discussions I see on gentoo-dev, I gather that it might be
possible to get a gcc-3.1 system up and running by either
1.) ebuilding gcc before anything else
2.) going easy on the optimizations
3.) switching profiles after the first bootstrap and re-bootstrapping

I also remember seeing something about the stage-1 image *requiring*
libstdc++-v2 and basically the gcc 2.x provided runtime which makes sense
because they have been compiled with gcc 2.x perhaps. But are they
statically linked binaries or is it necessary to provide a gcc 2.x runtime
during bootstrap?
Secondly, am I doing something wrong in using the 1.2 build image?
Thirdly, has anyone seen this kind of error before (atleast I don't see it
from what I gathered from the archives) and what insights could I have
into this?

Regards,
Prashanth Aditya Susarla

PS:- I'll try to reproduce the exact errors if I can but the basic problem
is that most binaries segfault soon after glibc is built.