Introduction

as it's safe even for the revdep-rebuild way Revision Changes Path 1.10 +12 -29 xml/htdocs/doc/en/gcc-upgrading.xml file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gcc-upgrading.xml?rev=1.10&content-type=text/x-cvsweb-markup&cvsroot=gentoo plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gcc-upgrading.xml?rev=1.10&content-type=text/plain&cvsroot=gentoo diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gcc-upgrading.xml.diff?r1=1.9&r2=1.10&cvsroot=gentoo Index: gcc-upgrading.xml =================================================================== RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v retrieving revision 1.9 retrieving revision 1.10 diff -u -r1.9 -r1.10 --- gcc-upgrading.xml 9 Feb 2006 17:40:19 -0000 1.9 +++ gcc-upgrading.xml 25 Feb 2006 09:37:33 -0000 1.10 @@ -1,5 +1,5 @@ - + @@ -25,8 +25,8 @@ -8 -2006-02-09 +9 +2006-02-25 Introduction @@ -394,40 +394,23 @@ that will affect the system compile.

-# emerge -uav gcc
-# gcc-config i686-pc-linux-gnu-3.4.4
-# source /etc/profile
-
-(Rebuilding libtool)
-# emerge --oneshot -av libtool
-

- - -This assumes that you have CHOST="i686-pc-linux-gnu" set. If you are -using another CHOST, please use the appropriate gcc-config line. - - -

-To provide compatibility with older binary C++ applications, -sys-libs/libstdc++-v3 needs to be merged onto your system. -

- -

-# emerge --oneshot sys-libs/libstdc++-v3
-

Since we are performing these actions after an initial installation, we do not -need to recompile the world target as we would when doing an upgrade on an -already installed system. However, you may choose to perform a world update in -place of the system update, to ensure that all packages are updated. +need to recompile the world target as we would when doing an upgrade on +an already installed system. However, you may choose to perform a world update +in place of the system update, to ensure that all packages are updated.

 # emerge -e system

+ +