/[gentoo]/xml/htdocs/doc/en/gcc-upgrading.xml
Gentoo

Diff of /xml/htdocs/doc/en/gcc-upgrading.xml

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.27 Revision 1.28
1<?xml version='1.0' encoding="UTF-8"?> 1<?xml version='1.0' encoding="UTF-8"?>
2<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.27 2008/05/19 21:02:24 swift Exp $ --> 2<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.28 2008/07/20 00:34:37 nightmorph Exp $ -->
3 3
4<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> 4<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
5 5
6<guide link="/doc/en/gcc-upgrading.xml"> 6<guide link="/doc/en/gcc-upgrading.xml">
7<title>Gentoo GCC Upgrade Guide</title> 7<title>Gentoo GCC Upgrade Guide</title>
11</author> 11</author>
12<author title="Author"> 12<author title="Author">
13 <mail link="jkt@gentoo.org">Jan Kundrát</mail> 13 <mail link="jkt@gentoo.org">Jan Kundrát</mail>
14</author> 14</author>
15<author title="Editor"> 15<author title="Editor">
16 <mail link="mark@halcy0n.com">Mark Loeser</mail> 16 <mail link="halcy0n"/>
17</author>
18<author title="Editor">
19 <mail link="nightmorph"/>
17</author> 20</author>
18 21
19<abstract> 22<abstract>
20This document will guide the user through the process of upgrading GCC on their 23This document will guide the user through the process of upgrading GCC on their
21Gentoo machines. 24Gentoo machines.
23 26
24<!-- The content of this document is licensed under the CC-BY-SA license --> 27<!-- The content of this document is licensed under the CC-BY-SA license -->
25<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> 28<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
26<license/> 29<license/>
27 30
28<version>22</version> 31<version>23</version>
29<date>2007-04-03</date> 32<date>2008-07-19</date>
30 33
31<chapter id="intro"> 34<chapter id="intro">
32<title>Introduction</title> 35<title>Introduction</title>
33<section> 36<section>
34<title>GCC Upgrading</title> 37<title>GCC Upgrading</title>
114# <i>gcc-config i686-pc-linux-gnu-4.1.1</i> 117# <i>gcc-config i686-pc-linux-gnu-4.1.1</i>
115# <i>env-update &amp;&amp; source /etc/profile</i> 118# <i>env-update &amp;&amp; source /etc/profile</i>
116 119
117<comment>If you upgraded from gcc 3 to 4 (e.g. from 3.4.6 to 4.1.1 in this 120<comment>If you upgraded from gcc 3 to 4 (e.g. from 3.4.6 to 4.1.1 in this
118example) you will have to run fix_libtool_files.sh manually</comment> 121example) you will have to run fix_libtool_files.sh manually</comment>
119# <i>fix_libtool_files.sh 3.4.6</i> 122<comment>(Replace $CHOST with your actual CHOST, found in /etc/make.conf)</comment>
123<comment>(Replace &lt;gcc-version&gt; with your new, updated GCC version)</comment>
124# <i>/usr/share/gcc-data/$CHOST/&lt;gcc-version&gt;/fix_libtool_files.sh 3.4.6</i>
120 125
121<comment>(Rebuilding libtool)</comment> 126<comment>(Rebuilding libtool)</comment>
122# <i>emerge --oneshot -av libtool</i> 127# <i>emerge --oneshot -av libtool</i>
123</pre> 128</pre>
124 129
278# <i>gcc-config i686-pc-linux-gnu-3.4.5</i> 283# <i>gcc-config i686-pc-linux-gnu-3.4.5</i>
279# <i>source /etc/profile</i> 284# <i>source /etc/profile</i>
280 285
281<comment>If you upgraded from gcc 3 to 4 (e.g. from 3.3.6 to 4.1.1 in this 286<comment>If you upgraded from gcc 3 to 4 (e.g. from 3.3.6 to 4.1.1 in this
282example) you will have to run fix_libtool_files.sh manually</comment> 287example) you will have to run fix_libtool_files.sh manually</comment>
283# <i>fix_libtool_files.sh 3.3.6</i> 288<comment>(Replace $CHOST with your actual CHOST, found in /etc/make.conf)</comment>
289<comment>(Replace &lt;gcc-version&gt; with your new, updated GCC version)</comment>
290# <i>/usr/share/gcc-data/$CHOST/&lt;gcc-version&gt;/fix_libtool_files.sh 3.3.6</i>
284 291
285<comment>(Rebuilding libtool)</comment> 292<comment>(Rebuilding libtool)</comment>
286# <i>emerge --oneshot -av libtool</i> 293# <i>emerge --oneshot -av libtool</i>
287</pre> 294</pre>
288 295
477<body> 484<body>
478 485
479<p> 486<p>
480If your system complains about something like <e>libtool: link: 487If your system complains about something like <e>libtool: link:
481`/usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.6/libstdc++.la' is not a valid libtool 488`/usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.6/libstdc++.la' is not a valid libtool
482archive</e>, please run <c>/sbin/fix_libtool_files.sh 3.3.6</c> (substitute 489archive</e>, please run
490<c>/usr/share/gcc-data/$CHOST/&lt;gcc-version&gt;/fix_libtool_files.sh 3.3.6</c>
483"3.3.6" with the version numbers from the error message). 491(substitute "3.3.6" with the version numbers from the error message, and $CHOST
492and &lt;gcc-version&gt; with your actual CHOST and GCC version).
484</p> 493</p>
485 494
486<p> 495<p>
487If you see <e>error: /usr/bin/gcc-config: line 632: 496If you see <e>error: /usr/bin/gcc-config: line 632:
488/etc/env.d/gcc/i686-pc-linux-gnu-3.3.5: No such file or directory</e>, then try 497/etc/env.d/gcc/i686-pc-linux-gnu-3.3.5: No such file or directory</e>, then try

Legend:
Removed from v.1.27  
changed lines
  Added in v.1.28

  ViewVC Help
Powered by ViewVC 1.1.20