| 1 |
Grant Edwards ha scritto: |
| 2 |
|
| 3 |
> I'll probably just do a clean reinstall at that point. When I |
| 4 |
> switched gcc from 3.2 to 3.3, it would have been a lot less |
| 5 |
> work to just re-install from scratch. |
| 6 |
|
| 7 |
My personal experience is that it is no more such a bad hassle. For |
| 8 |
upgrading to gcc 4.1.x you have to re-emerge ALL. This sounds tragic (it |
| 9 |
sounded tragic to me), but it's not. It's simply slow (It took about 5 |
| 10 |
days to recompile all my 900 packages on my old AMD Duron 1800...yes I |
| 11 |
know I install a lot of cruft that I forget to uninstall). You can |
| 12 |
easily have your system running happily while doing this. Just check |
| 13 |
that the emerge is running a couple of times a day (some package may |
| 14 |
fail here and there: in this case, just take note and emerge --resume |
| 15 |
--skipfirst. When it has all finished, you can care about it later). |
| 16 |
|
| 17 |
My personal rule of thumb is to wait AT LEAST a month after a new, |
| 18 |
incompatible GCC has been marked stable. That's because often many |
| 19 |
packages still fail/have troubles with the new compiler. In the first |
| 20 |
months all major hassles are ironed out, packages are upgraded |
| 21 |
accordingly and the transition becomes smooth. |
| 22 |
|
| 23 |
So, in going towards gcc 4.1 (something I delayed 6 months) you should |
| 24 |
have almost no problem. :) |
| 25 |
|
| 26 |
m. |
| 27 |
-- |
| 28 |
gentoo-user@g.o mailing list |
Archives