/[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.4 Revision 1.11
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.11 2004/10/02 21:53:56 cam 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.3</version>
19 <date>3 March 2003</date> 20<date>October 2, 2004</date>
20 21
21 <license/>
22 22
23 <abstract>A method for upgrading older Gentoo installations in place to Gentoo 1.4</abstract>
24 23
25 <chapter> 24 <chapter>
26 <title>Before you begin</title> 25 <title>Before you begin</title>
27 <section> 26 <section>
28 <title>Be prepared</title> 27 <title>Be prepared</title>
65 <title>Get Portage as current as possible</title> 64 <title>Get Portage as current as possible</title>
66 <body> 65 <body>
67 <p>Some of the syntax of current ebuilds is unreadable by 66 <p>Some of the syntax of current ebuilds is unreadable by
68 older versions of Portage. If you don't have at least Portage 2.0.44, try upgrading Portage.</p> 67 older versions of Portage. If you don't have at least Portage 2.0.44, try upgrading Portage.</p>
69 <pre> 68 <pre>
70# <i>emerge sync</i> 69# <i>emerge --sync</i>
71# <i>emerge -u portage</i> 70# <i>emerge -u portage</i>
72</pre> 71</pre>
73 <note>If your Portage version is very old, you may get an 72 <note>If your Portage version is very old, you may get an
74 error message containing the phrase "unscriptable object". 73 error message containing the phrase "unscriptable object".
75 Read and follow the instructions in 74 Read and follow the instructions in
94# <i>emerge -u gcc</i> 93# <i>emerge -u gcc</i>
95</pre> 94</pre>
96 95
97 <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>
98 <pre> 97 <pre>
99# <c>gcc-config --get-current-profile</c> 98# <i>gcc-config --get-current-profile</i>
100</pre> 99</pre>
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 <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>
102 </body> 101 </body>
103 </section> 102 </section>
104 <section> 103 <section>
111 version that is marked stable for your architecture. To see 110 version that is marked stable for your architecture. To see
112 if an ebuild is considered stable for your architecture, look 111 if an ebuild is considered stable for your architecture, look
113 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
114 architecture listed without a ~ in front of it, it is 113 architecture listed without a ~ in front of it, it is
115 considered stable. Assuming 3.2.2 is the most current stable 114 considered stable. Assuming 3.2.2 is the most current stable
116 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
117<pre> 131<pre>
118# <i>emerge /usr/portage/sys-devel/gcc/gcc-3.2.2.ebuild</i> 132# <i>USE="-java" emerge /usr/portage/sys-devel/gcc/gcc-3.2.2.ebuild</i>
119</pre> 133</pre>
120 </body> 134 </body>
121 </section> 135 </section>
122 <section> 136 <section>
123 <title>Changing profiles</title> 137 <title>Changing profiles</title>

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

  ViewVC Help
Powered by ViewVC 1.1.20