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