| 1 |
As a user who has done this on a number of systems - its no sweat. |
| 2 |
|
| 3 |
Also, check some of the older guides for upgrading from gcc-2.95 to 3, |
| 4 |
and 3.0 to 3.1 - should still be around somewhere. Its been done |
| 5 |
before, more than once - ask some of the older devs whove been around |
| 6 |
since the early days(!). |
| 7 |
|
| 8 |
Traps this time were uninstalling 3.3.6 without installing the |
| 9 |
sys-libs/libstdc++-v3 first. Ive put off removing 3.3.6 from the other |
| 10 |
systems until I get the nerve up again. |
| 11 |
|
| 12 |
So as well as instructions to do the task, some rescue for common |
| 13 |
mistakes like this would be nice. |
| 14 |
|
| 15 |
BillK |
| 16 |
|
| 17 |
On Tue, 2005-11-29 at 08:50 -0500, Curtis Napier wrote: |
| 18 |
> Speaking as a user who upgraded from 3.3.x to 3.4.x a loooooong loooong |
| 19 |
> time ago and also as a forum mod who sees questins about this on a daily |
| 20 |
> basis: |
| 21 |
> |
| 22 |
> Users are more or less aware that they will have to rebuild the entire |
| 23 |
> world including the kernel when they upgrade gcc. If they aren't already |
| 24 |
> aware of it they soon learn that it is necessary and they aren't averse |
| 25 |
> to it. This is a from source distro afterall, so TELLING them in an |
| 26 |
> upgrade guide that they *HAVE* to do this wouldn't be such a bad thing. |
| 27 |
> It solves 99% of all the problems reported in a gcc upgrade for people |
| 28 |
> who *didn't* do an "emerge -e world". |
| 29 |
> |
| 30 |
> Doing it from the outset will save the forums and bugs a lot of stress |
| 31 |
> and heartache that could have been easily avoided. |
| 32 |
> |
| 33 |
> Just my 2 $DENOMINATION's |
| 34 |
-- |
| 35 |
William Kenworthy <billk@×××××××××.au> |
| 36 |
Home! |
| 37 |
-- |
| 38 |
gentoo-dev@g.o mailing list |
Archives