nightmorph 06/08/31 00:08:58 Modified: gcc-upgrading.xml Log: Updated gcc guide for bug 145014, thanks to amne for the updates
Revision Changes Path 1.14 xml/htdocs/doc/en/gcc-upgrading.xml file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml?rev=1.14&view=markup plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml?rev=1.14&content-type=text/plain diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml?r1=1.13&r2=1.14 Index: gcc-upgrading.xml =================================================================== RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v retrieving revision 1.13 retrieving revision 1.14 diff -u -r1.13 -r1.14 --- gcc-upgrading.xml 26 May 2006 20:45:35 -0000 1.13 +++ gcc-upgrading.xml 31 Aug 2006 00:08:57 -0000 1.14 @@ -1,5 +1,5 @@ <?xml version='1.0' encoding="UTF-8"?> -<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.13 2006/05/26 20:45:35 nightmorph Exp $ --> +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.14 2006/08/31 00:08:57 nightmorph Exp $ --> <!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> @@ -25,8 +25,8 @@ <!-- See http://creativecommons.org/licenses/by-sa/2.5 --> <license/> -<version>12</version> -<date>2006-05-26</date> +<version>13</version> +<date>2006-08-30</date> <chapter id="intro"> <title>Introduction</title> @@ -107,18 +107,22 @@ <pre caption="Upgrading GCC"> # <i>emerge -uav gcc</i> -<comment>(Please substitute "i686-pc-linux-gnu-3.4.5" with the GCC +<comment>(Please substitute "i686-pc-linux-gnu-4.1.1" with the GCC version and CHOST settings you've upgraded to:)</comment> -# <i>gcc-config i686-pc-linux-gnu-3.4.5</i> +# <i>gcc-config i686-pc-linux-gnu-4.1.1</i> # <i>source /etc/profile</i> +<comment>If you upgraded from gcc 3 to 4 (e.g. from 3.4.6 to 4.1.1 in this +example) you will have to run fix_libtool_files.sh manually</comment> +# <i>fix_libtool_files.sh 3.4.6</i> + <comment>(Rebuilding libtool)</comment> # <i>emerge --oneshot -av libtool</i> </pre> <p> -Now let's rebuild toolchain and then world so we will make use of the new -compiler. +To be completely safe that your system is in a sane state, you <e>must</e> +rebuild the toolchain and then world to make use of the new compiler. </p> <pre caption="Rebuilding system"> @@ -129,11 +133,11 @@ <p> It is safe to remove the older GCC version at this time. If you feel the need, please issue the following command (as usual, substitute -<c>=sys-devel/gcc-3.3*</c> with the version you want to uninstall): +<c>=sys-devel/gcc-3.4*</c> with the version you want to uninstall): </p> <pre caption="Removing older GCC version"> -# <i>emerge -aC =sys-devel/gcc-3.3*</i> +# <i>emerge -aC =sys-devel/gcc-3.4*</i> </pre> </body> @@ -159,6 +163,11 @@ <body> <impo> +If you upgrade from gcc 3.4 to 4.1, please consult the General Update +instructions. +</impo> + +<impo> If you're upgrading on a SPARC machine, you will have to take the way of <uri link="#upgrade-3.3-to-3.4-emerge-e">complete system rebuild</uri> due to some internal <uri link="http://gcc.gnu.org/gcc-3.4/sparc-abi.html";>ABI @@ -166,13 +175,16 @@ </impo> <p> -You have two possibilities on how to upgrade your system. The <uri -link="#upgrade-3.3-to-3.4-revdep-rebuild">first method</uri> is faster and -requires use of the <c>revdep-rebuild</c> tool from package <c>gentoolkit</c> -while the <uri link="#upgrade-3.3-to-3.4-emerge-e">second one</uri> rebuilds the -entire system from scratch so it will make use of new GCC features. It's up to -you to decide which of these two ways you will choose. In most cases, the first -method is sufficient. +If you upgrade from gcc 3.3 to 3.4, you have two possibilities on how to +upgrade your system. The <uri link="#upgrade-3.3-to-3.4-revdep-rebuild">first +method</uri> is faster and requires use of the <c>revdep-rebuild</c> tool from +package <c>gentoolkit</c> while the <uri +link="#upgrade-3.3-to-3.4-emerge-e">second one</uri> rebuilds the entire +system from scratch so it will make use of new GCC features. It's up to you to decide which of these two ways you will choose. In most cases, the first +method is sufficient.</p> +<p>If you upgrade from gcc 3.3 to 4.1, do not use the method based on +revdep-rebuild, but do a <uri link="#upgrade-3.3-to-3.4-emerge-e">complete +system rebuild</uri>. </p> </body> @@ -249,6 +261,10 @@ # <i>gcc-config i686-pc-linux-gnu-3.4.5</i> # <i>source /etc/profile</i> +<comment>If you upgraded from gcc 3 to 4 (e.g. from 3.3.6 to 4.1.1 in this +example) you will have to run fix_libtool_files.sh manually</comment> +# <i>fix_libtool_files.sh 3.3.6</i> + <comment>(Rebuilding libtool)</comment> # <i>emerge --oneshot -av libtool</i> </pre> @@ -428,8 +444,8 @@ <p> Always use same GCC version for your kernel and additional kernel modules. Once you rebuild your world with new GCC, external modules (like -<c>app-emulation/qemu-softmmu</c>) will fail to load. Please rebuild your kernel -with new GCC to fix that. +<c>app-emulation/qemu-softmmu</c>) will fail to load. Please rebuild your +kernel with the new GCC to fix that. </p> <p> @@ -451,11 +467,11 @@ </p> <p> -If you see the <e>error: /usr/bin/gcc-config: line 632: +If you see <e>error: /usr/bin/gcc-config: line 632: /etc/env.d/gcc/i686-pc-linux-gnu-3.3.5: No such file or directory</e>, then try deleting <path>/etc/env.d/gcc/config-i686-pc-linux-gnu</path> and running -<c>gcc-config</c> again, followed by <c>source /etc/profile</c>. Only do this if -you do not have any cross-compilers set up, though. +<c>gcc-config</c> again, followed by <c>source /etc/profile</c>. Only do this +if you do not have any cross-compilers set up, though. </p> <p> -- [email protected] mailing list
