[gentoo-dev] Re: bootstrapping since gcc 3.4 is stable

[Sven Köhler]

>> I have no clue, what "bootstrap.sh" is for anymore.
>> For me, Installing gentoo was always like this:
>
> Ok, let me remind all. Stage 1 is a minimal system that is mainly built
> statically with the sole purpose of being suitable to build a working system
> from. It contains a cripled compiler as one of the first things it does is
> make a proper one. After that the original compiler should be gone. While
> some recompiling is needed because of circular dependencies between libc and
> gcc, this should be no issue. After the bootstrap has been run, one should
> have a proper minimal building environment that should be able to build all
> packages (except for some assumptions on available tools). This minimal
> environment is called stage 2.
>
> Stage 2 should not contain any trace of the bootstrap compiler. If the
> bootstrap compiler was a 3.3.x version and the final one a 3.4.x version,
> there should be no 3.3.x version remaining. Be aware though that if the
> profile does not offer a 3.4 compiler the final will be a 3.3 compiler. If
> desired the profile should be changed before running bootstrap.sh

I think that i clearly explained several times, that bootstrap.sh
installs gcc 3.4 _without_ removing the crippled gcc 3.3 that came with
stage1.

Mike Frysinger is talking about "choice" and ignores me if i tell him,
that the "emerge -e system" uses the crippled gcc 3.3 for the first 10
packages until "emerge -e system" finally rebuilds gcc 3.3 (only due to
some sideeffects!!! namely the dependy of gcc 3.4 on libstdc++-v3 OR gcc
3.3).

>> Mike is telling me, that the 2006.0 tarballs will contain gcc-3.4.
>> Then he's telling me, that the problem, that Im trying to point out, is
>> going to vanish with the release of the 2006.0 tarballs. Well, yes,
>> until the next gcc-slot becomes stable. So the problem is not fixed,
>> just moved to the future again.
>
> If a stage1 install does not remove a 3.3.x bootstrap compiler when a 3.4 is
> used as the main, that is a bug in the bootstrap script. As such it should be
> fixed.

So i see that you seem to agree with me! The crippled gcc contained in
the stage1 has to be removed by bootstrap.sh - and this is not done
automatically by the steps that bootstrap.sh performs.