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