|
Lines 107-124
Link Here
|
| 107 |
<pre caption="Upgrading GCC"> |
107 |
<pre caption="Upgrading GCC"> |
| 108 |
# <i>emerge -uav gcc</i> |
108 |
# <i>emerge -uav gcc</i> |
| 109 |
|
109 |
|
| 110 |
<comment>(Please substitute "i686-pc-linux-gnu-3.4.5" with the GCC |
110 |
<comment>(Please substitute "i686-pc-linux-gnu-4.1.1" with the GCC |
| 111 |
version and CHOST settings you've upgraded to:)</comment> |
111 |
version and CHOST settings you've upgraded to:)</comment> |
| 112 |
# <i>gcc-config i686-pc-linux-gnu-3.4.5</i> |
112 |
# <i>gcc-config i686-pc-linux-gnu-4.1.1</i> |
| 113 |
# <i>source /etc/profile</i> |
113 |
# <i>source /etc/profile</i> |
| 114 |
|
114 |
|
|
|
115 |
<comment>If you upgraded from gcc 3 to 4 (e.g. from 3.4.6 to 4.1.1 in this |
| 116 |
example) you will have to run fix_libtool_files.sh manually</comment> |
| 117 |
# <i>fix_libtool_files.sh 3.4.6</i> |
| 118 |
|
| 115 |
<comment>(Rebuilding libtool)</comment> |
119 |
<comment>(Rebuilding libtool)</comment> |
| 116 |
# <i>emerge --oneshot -av libtool</i> |
120 |
# <i>emerge --oneshot -av libtool</i> |
| 117 |
</pre> |
121 |
</pre> |
| 118 |
|
122 |
|
| 119 |
<p> |
123 |
<p> |
| 120 |
Now let's rebuild toolchain and then world so we will make use of the new |
124 |
To be completely safe that the system is in a sane state, it is necessary to |
| 121 |
compiler. |
125 |
rebuild toolchain and then world to make use of the new compiler. |
| 122 |
</p> |
126 |
</p> |
| 123 |
|
127 |
|
| 124 |
<pre caption="Rebuilding system"> |
128 |
<pre caption="Rebuilding system"> |
|
Lines 129-139
Link Here
|
| 129 |
<p> |
133 |
<p> |
| 130 |
It is safe to remove the older GCC version at this time. If you feel the need, |
134 |
It is safe to remove the older GCC version at this time. If you feel the need, |
| 131 |
please issue the following command (as usual, substitute |
135 |
please issue the following command (as usual, substitute |
| 132 |
<c>=sys-devel/gcc-3.3*</c> with the version you want to uninstall): |
136 |
<c>=sys-devel/gcc-3.4*</c> with the version you want to uninstall): |
| 133 |
</p> |
137 |
</p> |
| 134 |
|
138 |
|
| 135 |
<pre caption="Removing older GCC version"> |
139 |
<pre caption="Removing older GCC version"> |
| 136 |
# <i>emerge -aC =sys-devel/gcc-3.3*</i> |
140 |
# <i>emerge -aC =sys-devel/gcc-3.4*</i> |
| 137 |
</pre> |
141 |
</pre> |
| 138 |
|
142 |
|
| 139 |
</body> |
143 |
</body> |
|
Lines 159-164
Link Here
|
| 159 |
<body> |
163 |
<body> |
| 160 |
|
164 |
|
| 161 |
<impo> |
165 |
<impo> |
|
|
166 |
If you upgrade from gcc 3.4 to 4.1, please consult the General Update |
| 167 |
instructions. |
| 168 |
</impo> |
| 169 |
|
| 170 |
<impo> |
| 162 |
If you're upgrading on a SPARC machine, you will have to take the way of |
171 |
If you're upgrading on a SPARC machine, you will have to take the way of |
| 163 |
<uri link="#upgrade-3.3-to-3.4-emerge-e">complete system rebuild</uri> due to |
172 |
<uri link="#upgrade-3.3-to-3.4-emerge-e">complete system rebuild</uri> due to |
| 164 |
some internal <uri link="http://gcc.gnu.org/gcc-3.4/sparc-abi.html">ABI |
173 |
some internal <uri link="http://gcc.gnu.org/gcc-3.4/sparc-abi.html">ABI |
|
Lines 166-178
Link Here
|
| 166 |
</impo> |
175 |
</impo> |
| 167 |
|
176 |
|
| 168 |
<p> |
177 |
<p> |
| 169 |
You have two possibilities on how to upgrade your system. The <uri |
178 |
If you upgrade from gcc 3.3 to 3.4, you have two possibilities on how to |
| 170 |
link="#upgrade-3.3-to-3.4-revdep-rebuild">first method</uri> is faster and |
179 |
upgrade your system. The <uri link="#upgrade-3.3-to-3.4-revdep-rebuild">first |
| 171 |
requires use of the <c>revdep-rebuild</c> tool from package <c>gentoolkit</c> |
180 |
method</uri> is faster and requires use of the <c>revdep-rebuild</c> tool from |
| 172 |
while the <uri link="#upgrade-3.3-to-3.4-emerge-e">second one</uri> rebuilds the |
181 |
package <c>gentoolkit</c> while the <uri |
| 173 |
entire system from scratch so it will make use of new GCC features. It's up to |
182 |
link="#upgrade-3.3-to-3.4-emerge-e">second one</uri> rebuilds the entire |
| 174 |
you to decide which of these two ways you will choose. In most cases, the first |
183 |
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 |
| 175 |
method is sufficient. |
184 |
method is sufficient.</p> |
|
|
185 |
<p>If you upgrade from gcc 3.3 to 4.1, do not use the method based on |
| 186 |
revdep-rebuild, but do a <uri link="#upgrade-3.3-to-3.4-emerge-e">complete |
| 187 |
system rebuild</uri>. |
| 176 |
</p> |
188 |
</p> |
| 177 |
|
189 |
|
| 178 |
</body> |
190 |
</body> |
|
Lines 249-254
Link Here
|
| 249 |
# <i>gcc-config i686-pc-linux-gnu-3.4.5</i> |
261 |
# <i>gcc-config i686-pc-linux-gnu-3.4.5</i> |
| 250 |
# <i>source /etc/profile</i> |
262 |
# <i>source /etc/profile</i> |
| 251 |
|
263 |
|
|
|
264 |
<comment>If you upgraded from gcc 3 to 4 (e.g. from 3.3.6 to 4.1.1 in this |
| 265 |
example) you will have to run fix_libtool_files.sh manually</comment> |
| 266 |
# <i>fix_libtool_files.sh 3.3.6</i> |
| 267 |
|
| 252 |
<comment>(Rebuilding libtool)</comment> |
268 |
<comment>(Rebuilding libtool)</comment> |
| 253 |
# <i>emerge --oneshot -av libtool</i> |
269 |
# <i>emerge --oneshot -av libtool</i> |
| 254 |
</pre> |
270 |
</pre> |
