| 1 |
On Wednesday 25 January 2006 21:40, Sven Köhler wrote: |
| 2 |
> I expected the result of these steps to be a "clean" system. |
| 3 |
> |
| 4 |
> What do i mean with a "clean" system? |
| 5 |
> |
| 6 |
> Actually i thought, that i mean the result of a "emerge -e system" - but |
| 7 |
> i know now, that this is not what i mean. For example "emerge -e system" |
| 8 |
> sometimes choses to install gcc-3.3 instead of the "default" libstdc++-v3. |
| 9 |
|
| 10 |
what you want to happen just isnt feasible at this point in time (if it ever |
| 11 |
will be) |
| 12 |
|
| 13 |
portage does not automatically change the version of gcc across major |
| 14 |
versions ... this is done on purpose as there is no way of knowing whether |
| 15 |
the user wants the new version of gcc to be the default system one or whether |
| 16 |
they are just installing a new one for fun |
| 17 |
|
| 18 |
you want bootstrap.sh to basically automatically run `emerge gcc && emerge |
| 19 |
prune gcc` ... this is not doable as packages may be tied to the older |
| 20 |
version of gcc ... and in fact, python itself currently links against |
| 21 |
libstdc++, so if bootstrap followed the automated steps listed above, you'd |
| 22 |
end up with a broken python (and thus a broken emerge) |
| 23 |
|
| 24 |
thus, in order to get a "clean" system you're so keen on, you need to run |
| 25 |
bootstrap.sh to get a 3.4 compiler, switch your default compiler to 3.4, |
| 26 |
rebuild anything that is linked against 3.3 with 3.4, prune 3.3 from your |
| 27 |
system, and then continue on with the `emerge -e system` |
| 28 |
-mike |
| 29 |
|
| 30 |
-- |
| 31 |
gentoo-dev@g.o mailing list |
Archives