| 1 |
jkt 06/02/09 16:15:21 |
| 2 |
|
| 3 |
Modified: xml/htdocs/doc/en gcc-upgrading.xml |
| 4 |
Log: |
| 5 |
Moving the "common-pitfalls" section to the end of the document |
| 6 |
|
| 7 |
Revision Changes Path |
| 8 |
1.8 +65 -65 xml/htdocs/doc/en/gcc-upgrading.xml |
| 9 |
|
| 10 |
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 |
| 11 |
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 |
| 12 |
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 |
| 13 |
|
| 14 |
Index: gcc-upgrading.xml |
| 15 |
=================================================================== |
| 16 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v |
| 17 |
retrieving revision 1.7 |
| 18 |
retrieving revision 1.8 |
| 19 |
diff -u -r1.7 -r1.8 |
| 20 |
--- gcc-upgrading.xml 9 Feb 2006 16:06:51 -0000 1.7 |
| 21 |
+++ gcc-upgrading.xml 9 Feb 2006 16:15:21 -0000 1.8 |
| 22 |
@@ -1,5 +1,5 @@ |
| 23 |
<?xml version='1.0' encoding="UTF-8"?> |
| 24 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.7 2006/02/09 16:06:51 jkt Exp $ --> |
| 25 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.8 2006/02/09 16:15:21 jkt Exp $ --> |
| 26 |
|
| 27 |
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
| 28 |
|
| 29 |
@@ -25,7 +25,7 @@ |
| 30 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
| 31 |
<license/> |
| 32 |
|
| 33 |
-<version>6</version> |
| 34 |
+<version>7</version> |
| 35 |
<date>2006-02-09</date> |
| 36 |
|
| 37 |
<chapter id="intro"> |
| 38 |
@@ -295,69 +295,6 @@ |
| 39 |
</section> |
| 40 |
</chapter> |
| 41 |
|
| 42 |
-<chapter id="common-pitfalls"> |
| 43 |
-<title>Common Pitfalls</title> |
| 44 |
-<section> |
| 45 |
-<body> |
| 46 |
- |
| 47 |
-<p> |
| 48 |
-It's important to disable <c>distcc</c> during upgrade. Mixing compiler versions |
| 49 |
-on your nodes <e>will</e> cause build issues. This is not required for ccache, |
| 50 |
-as the cache objects will be invalidated anyway. |
| 51 |
-</p> |
| 52 |
- |
| 53 |
-<p> |
| 54 |
-Always use same GCC version for your kernel and additional kernel modules. Once |
| 55 |
-you rebuild your world with new GCC, external modules (like |
| 56 |
-<c>app-emulation/qemu-softmmu</c>) will fail to load. Please rebuild your kernel |
| 57 |
-with new GCC to fix that. |
| 58 |
-</p> |
| 59 |
- |
| 60 |
-</body> |
| 61 |
-</section> |
| 62 |
-<section> |
| 63 |
-<title>Frequent Error Messages</title> |
| 64 |
-<body> |
| 65 |
- |
| 66 |
-<p> |
| 67 |
-If your system complains about something like <e>libtool: link: |
| 68 |
-`/usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.6/libstdc++.la' is not a valid libtool |
| 69 |
-archive</e>, please run <c>/sbin/fix_libtool_files.sh 3.3.6</c> (substitute |
| 70 |
-"3.3.6" with the version numbers from the error message). |
| 71 |
-</p> |
| 72 |
- |
| 73 |
-<p> |
| 74 |
-If you see the <e>error: /usr/bin/gcc-config: line 632: |
| 75 |
-/etc/env.d/gcc/i686-pc-linux-gnu-3.3.5: No such file or directory</e>, then try |
| 76 |
-deleting <path>/etc/env.d/gcc/config-i686-pc-linux-gnu</path> and running |
| 77 |
-<c>gcc-config</c> again, followed by <c>source /etc/profile</c>. Only do this if |
| 78 |
-you do not have any cross-compilers set up, though. |
| 79 |
-</p> |
| 80 |
- |
| 81 |
-<p> |
| 82 |
-If a package fails during <c>emerge -e system</c> or <c>emerge -e world</c>, |
| 83 |
-you can resume operation with <c>emerge --resume</c>. If a package fails |
| 84 |
-repeatedly, skip it with <c>emerge --resume --skipfirst</c>. Don't run any |
| 85 |
-other instances of emerge in between or you will lose the resume information. |
| 86 |
-</p> |
| 87 |
- |
| 88 |
-<p> |
| 89 |
-If you get an error message <e>spec failure: unrecognized spec option</e> while |
| 90 |
-upgrading your compiler, try to switch back to your default compiler, unset the |
| 91 |
-<c>GCC_SPECS</c> variable and upgrade GCC again: |
| 92 |
-</p> |
| 93 |
- |
| 94 |
-<pre caption="Restoring primary specs"> |
| 95 |
-# <i>gcc-config 1</i> |
| 96 |
-# <i>source /etc/profile</i> |
| 97 |
-# <i>unset GCC_SPECS</i> |
| 98 |
-# <i>emerge -uav gcc</i> |
| 99 |
-</pre> |
| 100 |
- |
| 101 |
-</body> |
| 102 |
-</section> |
| 103 |
-</chapter> |
| 104 |
- |
| 105 |
<chapter id="first-install"> |
| 106 |
<title>Upgrading to GCC on a First Install</title> |
| 107 |
<section> |
| 108 |
@@ -503,4 +440,67 @@ |
| 109 |
</body> |
| 110 |
</section> |
| 111 |
</chapter> |
| 112 |
+ |
| 113 |
+<chapter id="common-pitfalls"> |
| 114 |
+<title>Common Pitfalls</title> |
| 115 |
+<section> |
| 116 |
+<body> |
| 117 |
+ |
| 118 |
+<p> |
| 119 |
+It's important to disable <c>distcc</c> during upgrade. Mixing compiler versions |
| 120 |
+on your nodes <e>will</e> cause build issues. This is not required for ccache, |
| 121 |
+as the cache objects will be invalidated anyway. |
| 122 |
+</p> |
| 123 |
+ |
| 124 |
+<p> |
| 125 |
+Always use same GCC version for your kernel and additional kernel modules. Once |
| 126 |
+you rebuild your world with new GCC, external modules (like |
| 127 |
+<c>app-emulation/qemu-softmmu</c>) will fail to load. Please rebuild your kernel |
| 128 |
+with new GCC to fix that. |
| 129 |
+</p> |
| 130 |
+ |
| 131 |
+</body> |
| 132 |
+</section> |
| 133 |
+<section> |
| 134 |
+<title>Frequent Error Messages</title> |
| 135 |
+<body> |
| 136 |
+ |
| 137 |
+<p> |
| 138 |
+If your system complains about something like <e>libtool: link: |
| 139 |
+`/usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.6/libstdc++.la' is not a valid libtool |
| 140 |
+archive</e>, please run <c>/sbin/fix_libtool_files.sh 3.3.6</c> (substitute |
| 141 |
+"3.3.6" with the version numbers from the error message). |
| 142 |
+</p> |
| 143 |
+ |
| 144 |
+<p> |
| 145 |
+If you see the <e>error: /usr/bin/gcc-config: line 632: |
| 146 |
+/etc/env.d/gcc/i686-pc-linux-gnu-3.3.5: No such file or directory</e>, then try |
| 147 |
+deleting <path>/etc/env.d/gcc/config-i686-pc-linux-gnu</path> and running |
| 148 |
+<c>gcc-config</c> again, followed by <c>source /etc/profile</c>. Only do this if |
| 149 |
+you do not have any cross-compilers set up, though. |
| 150 |
+</p> |
| 151 |
+ |
| 152 |
+<p> |
| 153 |
+If a package fails during <c>emerge -e system</c> or <c>emerge -e world</c>, |
| 154 |
+you can resume operation with <c>emerge --resume</c>. If a package fails |
| 155 |
+repeatedly, skip it with <c>emerge --resume --skipfirst</c>. Don't run any |
| 156 |
+other instances of emerge in between or you will lose the resume information. |
| 157 |
+</p> |
| 158 |
+ |
| 159 |
+<p> |
| 160 |
+If you get an error message <e>spec failure: unrecognized spec option</e> while |
| 161 |
+upgrading your compiler, try to switch back to your default compiler, unset the |
| 162 |
+<c>GCC_SPECS</c> variable and upgrade GCC again: |
| 163 |
+</p> |
| 164 |
+ |
| 165 |
+<pre caption="Restoring primary specs"> |
| 166 |
+# <i>gcc-config 1</i> |
| 167 |
+# <i>source /etc/profile</i> |
| 168 |
+# <i>unset GCC_SPECS</i> |
| 169 |
+# <i>emerge -uav gcc</i> |
| 170 |
+</pre> |
| 171 |
+ |
| 172 |
+</body> |
| 173 |
+</section> |
| 174 |
+</chapter> |
| 175 |
</guide> |
| 176 |
|
| 177 |
|
| 178 |
|
| 179 |
-- |
| 180 |
gentoo-doc-cvs@g.o mailing list |
Archives