/[gentoo]/xml/htdocs/doc/en/new-upgrade-to-gentoo-1.4.xml
Gentoo

Diff of /xml/htdocs/doc/en/new-upgrade-to-gentoo-1.4.xml

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

Revision 1.1 Revision 1.10
1<?xml version='1.0' encoding="UTF-8"?> 1<?xml version='1.0' encoding="UTF-8"?>
2<?xml-stylesheet href="/xsl/guide.xsl" type="text/xsl"?> 2<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/new-upgrade-to-gentoo-1.4.xml,v 1.10 2004/09/23 12:23:42 swift Exp $ -->
3
4<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> 3<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
5 4
6<guide link="/doc/lang/new-upgrade-to-gentoo-1.4.xml"> 5<guide link="new-upgrade-to-gentoo-1.4.xml">
7 6
8<title>Gentoo 1.4 Upgrade Guide</title> 7<title>Gentoo 1.4 Upgrade Guide</title>
9 8
10 <author title = "Author"> 9 <author title = "Author">
11<mail link = "rac@gentoo.org">Robert Coie</mail> 10<mail link = "rac@gentoo.org">Robert Coie</mail>
13 12
14 <author title = "Copy Editor"> 13 <author title = "Copy Editor">
15<mail link = "avenj@gentoo.org">Jon Portnoy</mail> 14<mail link = "avenj@gentoo.org">Jon Portnoy</mail>
16</author> 15</author>
17 16
17 <abstract>A method for upgrading older Gentoo installations in place to Gentoo 1.4</abstract>
18 <license/>
18 <version>0.1</version> 19<version>0.2</version>
19 <date>3 March 2003</date> 20<date>September 23, 2004</date>
20 21
21 <abstract>A method for upgrading older Gentoo installations in place to Gentoo 1.4</abstract> 22
22 23
23 <chapter> 24 <chapter>
24 <title>Before you begin</title> 25 <title>Before you begin</title>
25 <section> 26 <section>
26 <title>Be prepared</title> 27 <title>Be prepared</title>
92# <i>emerge -u gcc</i> 93# <i>emerge -u gcc</i>
93</pre> 94</pre>
94 95
95 <p>You can now check to see if gcc-config is working properly:</p> 96 <p>You can now check to see if gcc-config is working properly:</p>
96 <pre> 97 <pre>
97# <c>gcc-config --get-current-profile</c> 98# <i>gcc-config --get-current-profile</i>
98</pre> 99</pre>
99 <p>This should return i686-pc-linux-gnu-2.95.3 on most systems. Older systems may return i586-pc-linux-gnu-2.95.3.</p> 100 <p>This should return i686-pc-linux-gnu-2.95.3 on most x86 systems. Older systems may return i586-pc-linux-gnu-2.95.3.</p>
100 </body> 101 </body>
101 </section> 102 </section>
102 <section> 103 <section>
103 <title>Installing GCC 3</title> 104 <title>Installing GCC 3</title>
104 <body> 105 <body>
109 version that is marked stable for your architecture. To see 110 version that is marked stable for your architecture. To see
110 if an ebuild is considered stable for your architecture, look 111 if an ebuild is considered stable for your architecture, look
111 for the KEYWORDS line in the ebuild file. If it has your 112 for the KEYWORDS line in the ebuild file. If it has your
112 architecture listed without a ~ in front of it, it is 113 architecture listed without a ~ in front of it, it is
113 considered stable. Assuming 3.2.2 is the most current stable 114 considered stable. Assuming 3.2.2 is the most current stable
114 version, then issue the following command:</p> 115 version, we first need to remove the glibc dependency from gcc.</p>
116
117<p>
118Edit <path>/usr/portage/sys-devel/gcc/gcc-3.2.2.ebuild</path> and search for the
119line containing <c>DEPEND</c>. Remove the <c>glibc</c> dependency and save the
120ebuild.
121</p>
122
123<pre caption="Editing gcc-3.2.2.ebuild">
124# <i>vim /usr/portage/sys-devel/gcc/gcc-3.2.2.ebuild</i>
125</pre>
126
127<p>
128Now install the latest GCC version on your system:
129</p>
130
115<pre> 131<pre>
116# <i>emerge /usr/portage/sys-apps/gcc/gcc-3.2.2.ebuild</i> 132# <i>USE="-java" emerge /usr/portage/sys-devel/gcc/gcc-3.2.2.ebuild</i>
117</pre> 133</pre>
118 </body> 134 </body>
119 </section> 135 </section>
120 <section> 136 <section>
121 <title>Changing profiles</title> 137 <title>Changing profiles</title>
157 <body><p>Now you may recompile everything on your system with 173 <body><p>Now you may recompile everything on your system with
158 your new compiler:</p> 174 your new compiler:</p>
159<pre> 175<pre>
160# <i>emerge -e world</i> 176# <i>emerge -e world</i>
161</pre> 177</pre>
178 <note>If this command fails at any point due to errors, you
179 can use <c>emerge --resume</c> to continue the process where
180 you left off. This requires Portage 2.0.47 or later.</note>
162 </body> 181 </body>
163 </section> 182 </section>
164 </chapter> 183 </chapter>
165</guide> 184</guide>
166 185

Legend:
Removed from v.1.1  
changed lines
  Added in v.1.10

  ViewVC Help
Powered by ViewVC 1.1.20