On Thursday 26 January 2006 13:23, Sven Köhler wrote: > You say, that it's the intended behaviour, that bootstrap.sh keeps the > crippled gcc 3.3 intact and as the default compiler.
ok, i looked into this some more and ran some tests ... long and short of it is that the behavior i discussed before applies only in a stage3 and beyond ... the gcc-config logic is specifically tweaked during bootstrap and build (i.e. stage1 and stage2), thus everything i said wrt to automatic switching of gcc has no bearing on this discussion ive chatted with wolf and the real fix here is to change the 'emerge clean' at the end of bootstrap.sh into an 'emerge prune sys-devel/gcc' ... that way when you emerge a new SLOT-ed version of gcc, the old stripped down version in stage1 is automatically pruned -mike -- [email protected] mailing list
