1 |
>> You say, that it's the intended behaviour, that bootstrap.sh keeps the |
2 |
>> crippled gcc 3.3 intact and as the default compiler. |
3 |
> |
4 |
> ok, i looked into this some more and ran some tests ... |
5 |
> |
6 |
> long and short of it is that the behavior i discussed before applies only in a |
7 |
> stage3 and beyond ... the gcc-config logic is specifically tweaked during |
8 |
> bootstrap and build (i.e. stage1 and stage2), thus everything i said wrt to |
9 |
> automatic switching of gcc has no bearing on this discussion |
10 |
> |
11 |
> ive chatted with wolf and the real fix here is to change the 'emerge clean' at |
12 |
> the end of bootstrap.sh into an 'emerge prune sys-devel/gcc' ... that way |
13 |
> when you emerge a new SLOT-ed version of gcc, the old stripped down version |
14 |
> in stage1 is automatically pruned |
15 |
|
16 |
I also noticed the "--oneshot" fix. |
17 |
|
18 |
Thank you! |