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