/[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.4
15<mail link = "avenj@gentoo.org">Jon Portnoy</mail> 15<mail link = "avenj@gentoo.org">Jon Portnoy</mail>
16</author> 16</author>
17 17
18 <version>0.1</version> 18 <version>0.1</version>
19 <date>3 March 2003</date> 19 <date>3 March 2003</date>
20
21 <license/>
20 22
21 <abstract>A method for upgrading older Gentoo installations in place to Gentoo 1.4</abstract> 23 <abstract>A method for upgrading older Gentoo installations in place to Gentoo 1.4</abstract>
22 24
23 <chapter> 25 <chapter>
24 <title>Before you begin</title> 26 <title>Before you begin</title>
94 96
95 <p>You can now check to see if gcc-config is working properly:</p> 97 <p>You can now check to see if gcc-config is working properly:</p>
96 <pre> 98 <pre>
97# <c>gcc-config --get-current-profile</c> 99# <c>gcc-config --get-current-profile</c>
98</pre> 100</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> 101 <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> 102 </body>
101 </section> 103 </section>
102 <section> 104 <section>
103 <title>Installing GCC 3</title> 105 <title>Installing GCC 3</title>
104 <body> 106 <body>
111 for the KEYWORDS line in the ebuild file. If it has your 113 for the KEYWORDS line in the ebuild file. If it has your
112 architecture listed without a ~ in front of it, it is 114 architecture listed without a ~ in front of it, it is
113 considered stable. Assuming 3.2.2 is the most current stable 115 considered stable. Assuming 3.2.2 is the most current stable
114 version, then issue the following command:</p> 116 version, then issue the following command:</p>
115<pre> 117<pre>
116# <i>emerge /usr/portage/sys-apps/gcc/gcc-3.2.2.ebuild</i> 118# <i>emerge /usr/portage/sys-devel/gcc/gcc-3.2.2.ebuild</i>
117</pre> 119</pre>
118 </body> 120 </body>
119 </section> 121 </section>
120 <section> 122 <section>
121 <title>Changing profiles</title> 123 <title>Changing profiles</title>
157 <body><p>Now you may recompile everything on your system with 159 <body><p>Now you may recompile everything on your system with
158 your new compiler:</p> 160 your new compiler:</p>
159<pre> 161<pre>
160# <i>emerge -e world</i> 162# <i>emerge -e world</i>
161</pre> 163</pre>
164 <note>If this command fails at any point due to errors, you
165 can use <c>emerge --resume</c> to continue the process where
166 you left off. This requires Portage 2.0.47 or later.</note>
162 </body> 167 </body>
163 </section> 168 </section>
164 </chapter> 169 </chapter>
165</guide> 170</guide>
166 171

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

  ViewVC Help
Powered by ViewVC 1.1.20