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

[Mike Frysinger <vapier@gentoo.org>]

On Wednesday 25 January 2006 21:40, Sven Köhler wrote:
> I expected the result of these steps to be a "clean" system.
>
> What do i mean with a "clean" system?
>
> Actually i thought, that i mean the result of a "emerge -e system" - but
> i know now, that this is not what i mean. For example "emerge -e system"
> sometimes choses to install gcc-3.3 instead of the "default" libstdc++-v3.

what you want to happen just isnt feasible at this point in time (if it ever 
will be)

portage does not automatically change the version of gcc across major 
versions ... this is done on purpose as there is no way of knowing whether 
the user wants the new version of gcc to be the default system one or whether 
they are just installing a new one for fun

you want bootstrap.sh to basically automatically run `emerge gcc && emerge 
prune gcc` ... this is not doable as packages may be tied to the older 
version of gcc ... and in fact, python itself currently links against 
libstdc++, so if bootstrap followed the automated steps listed above, you'd 
end up with a broken python (and thus a broken emerge)

thus, in order to get a "clean" system you're so keen on, you need to run 
bootstrap.sh to get a 3.4 compiler, switch your default compiler to 3.4, 
rebuild anything that is linked against 3.3 with 3.4, prune 3.3 from your 
system, and then continue on with the `emerge -e system`
-mike

-- 
gentoo-dev@gentoo.org mailing list