jkt 06/02/09 16:15:21 Modified: xml/htdocs/doc/en gcc-upgrading.xml Log: Moving the "common-pitfalls" section to the end of the document
Revision Changes Path 1.8 +65 -65 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.8&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.8&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.7&r2=1.8&cvsroot=gentoo Index: gcc-upgrading.xml =================================================================== RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v retrieving revision 1.7 retrieving revision 1.8 diff -u -r1.7 -r1.8 --- gcc-upgrading.xml 9 Feb 2006 16:06:51 -0000 1.7 +++ gcc-upgrading.xml 9 Feb 2006 16:15:21 -0000 1.8 @@ -1,5 +1,5 @@ <?xml version='1.0' encoding="UTF-8"?> -<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.7 2006/02/09 16:06:51 jkt Exp $ --> +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.8 2006/02/09 16:15:21 jkt Exp $ --> <!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> @@ -25,7 +25,7 @@ <!-- See http://creativecommons.org/licenses/by-sa/2.5 --> <license/> -<version>6</version> +<version>7</version> <date>2006-02-09</date> <chapter id="intro"> @@ -295,69 +295,6 @@ </section> </chapter> -<chapter id="common-pitfalls"> -<title>Common Pitfalls</title> -<section> -<body> - -<p> -It's important to disable <c>distcc</c> during upgrade. Mixing compiler versions -on your nodes <e>will</e> cause build issues. This is not required for ccache, -as the cache objects will be invalidated anyway. -</p> - -<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. -</p> - -</body> -</section> -<section> -<title>Frequent Error Messages</title> -<body> - -<p> -If your system complains about something like <e>libtool: link: -`/usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.6/libstdc++.la' is not a valid libtool -archive</e>, please run <c>/sbin/fix_libtool_files.sh 3.3.6</c> (substitute -"3.3.6" with the version numbers from the error message). -</p> - -<p> -If you see the <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. -</p> - -<p> -If a package fails during <c>emerge -e system</c> or <c>emerge -e world</c>, -you can resume operation with <c>emerge --resume</c>. If a package fails -repeatedly, skip it with <c>emerge --resume --skipfirst</c>. Don't run any -other instances of emerge in between or you will lose the resume information. -</p> - -<p> -If you get an error message <e>spec failure: unrecognized spec option</e> while -upgrading your compiler, try to switch back to your default compiler, unset the -<c>GCC_SPECS</c> variable and upgrade GCC again: -</p> - -<pre caption="Restoring primary specs"> -# <i>gcc-config 1</i> -# <i>source /etc/profile</i> -# <i>unset GCC_SPECS</i> -# <i>emerge -uav gcc</i> -</pre> - -</body> -</section> -</chapter> - <chapter id="first-install"> <title>Upgrading to GCC on a First Install</title> <section> @@ -503,4 +440,67 @@ </body> </section> </chapter> + +<chapter id="common-pitfalls"> +<title>Common Pitfalls</title> +<section> +<body> + +<p> +It's important to disable <c>distcc</c> during upgrade. Mixing compiler versions +on your nodes <e>will</e> cause build issues. This is not required for ccache, +as the cache objects will be invalidated anyway. +</p> + +<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. +</p> + +</body> +</section> +<section> +<title>Frequent Error Messages</title> +<body> + +<p> +If your system complains about something like <e>libtool: link: +`/usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.6/libstdc++.la' is not a valid libtool +archive</e>, please run <c>/sbin/fix_libtool_files.sh 3.3.6</c> (substitute +"3.3.6" with the version numbers from the error message). +</p> + +<p> +If you see the <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. +</p> + +<p> +If a package fails during <c>emerge -e system</c> or <c>emerge -e world</c>, +you can resume operation with <c>emerge --resume</c>. If a package fails +repeatedly, skip it with <c>emerge --resume --skipfirst</c>. Don't run any +other instances of emerge in between or you will lose the resume information. +</p> + +<p> +If you get an error message <e>spec failure: unrecognized spec option</e> while +upgrading your compiler, try to switch back to your default compiler, unset the +<c>GCC_SPECS</c> variable and upgrade GCC again: +</p> + +<pre caption="Restoring primary specs"> +# <i>gcc-config 1</i> +# <i>source /etc/profile</i> +# <i>unset GCC_SPECS</i> +# <i>emerge -uav gcc</i> +</pre> + +</body> +</section> +</chapter> </guide> -- [email protected] mailing list
