/[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.9 Revision 1.10
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/new-upgrade-to-gentoo-1.4.xml,v 1.9 2004/09/17 09:46:34 swift Exp $ --> 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<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> 3<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
4 4
5<guide link="new-upgrade-to-gentoo-1.4.xml"> 5<guide link="new-upgrade-to-gentoo-1.4.xml">
6 6
7<title>Gentoo 1.4 Upgrade Guide</title> 7<title>Gentoo 1.4 Upgrade Guide</title>
8 8
9 <author title = "Author"> 9 <author title = "Author">
10<mail link = "rac@gentoo.org">Robert Coie</mail> 10<mail link = "rac@gentoo.org">Robert Coie</mail>
11</author> 11</author>
12 12
13 <author title = "Copy Editor"> 13 <author title = "Copy Editor">
14<mail link = "avenj@gentoo.org">Jon Portnoy</mail> 14<mail link = "avenj@gentoo.org">Jon Portnoy</mail>
15</author> 15</author>
16 16
17 <abstract>A method for upgrading older Gentoo installations in place to Gentoo 1.4</abstract> 17 <abstract>A method for upgrading older Gentoo installations in place to Gentoo 1.4</abstract>
18 <license/> 18 <license/>
19 <version>0.1</version> 19<version>0.2</version>
20 <date>3 March 2003</date> 20<date>September 23, 2004</date>
21 21
22 22
23 23
24 <chapter> 24 <chapter>
25 <title>Before you begin</title> 25 <title>Before you begin</title>
26 <section> 26 <section>
27 <title>Be prepared</title> 27 <title>Be prepared</title>
28 <body> 28 <body>
29 <p>As with any major upgrade to the core of your Gentoo 29 <p>As with any major upgrade to the core of your Gentoo
30 system, there is always the possibility that unforeseen 30 system, there is always the possibility that unforeseen
31 problems will ensue. It is always prudent to back up all 31 problems will ensue. It is always prudent to back up all
32 important data before beginning this process. If possible, 32 important data before beginning this process. If possible,
33 try to allocate a large block of time for this upgrade, so 33 try to allocate a large block of time for this upgrade, so
34 that you will not feel rushed. All the software on your 34 that you will not feel rushed. All the software on your
35 machine will need to be recompiled.</p> 35 machine will need to be recompiled.</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 <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>
101 </body> 101 </body>
102 </section> 102 </section>
103 <section> 103 <section>
104 <title>Installing GCC 3</title> 104 <title>Installing GCC 3</title>
105 <body> 105 <body>
106 <p>Now you can install a newer version of GCC without damaging 106 <p>Now you can install a newer version of GCC without damaging
107 your current compiler. Look in 107 your current compiler. Look in
108 <path>/usr/portage/sys-devel/gcc</path> for a version of the 108 <path>/usr/portage/sys-devel/gcc</path> for a version of the
109 GCC ebuild that is at least 3.2.1-r6. Choose the highest 109 GCC ebuild that is at least 3.2.1-r6. Choose the highest
110 version that is marked stable for your architecture. To see 110 version that is marked stable for your architecture. To see
111 if an ebuild is considered stable for your architecture, look 111 if an ebuild is considered stable for your architecture, look
112 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
113 architecture listed without a ~ in front of it, it is 113 architecture listed without a ~ in front of it, it is
114 considered stable. Assuming 3.2.2 is the most current stable 114 considered stable. Assuming 3.2.2 is the most current stable
115 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
116<pre> 131<pre>
117# <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>
118</pre> 133</pre>
119 </body> 134 </body>
120 </section> 135 </section>
121 <section> 136 <section>
122 <title>Changing profiles</title> 137 <title>Changing profiles</title>
123 <body> 138 <body>
124 <p>Now you need to change two sets of profiles: your 139 <p>Now you need to change two sets of profiles: your
125 gcc-config profile and your Portage profile.</p> 140 gcc-config profile and your Portage profile.</p>
126 <pre> 141 <pre>
127# <i>cd /etc</i> 142# <i>cd /etc</i>
128# <i>rm make.profile</i> 143# <i>rm make.profile</i>
129# <i>ln -s ../usr/portage/profiles/default-x86-1.4 make.profile</i> <codenote>Replace "x86" with your architecture</codenote> 144# <i>ln -s ../usr/portage/profiles/default-x86-1.4 make.profile</i> <codenote>Replace "x86" with your architecture</codenote>
130</pre> 145</pre>
131 146
132 <pre> 147 <pre>

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

  ViewVC Help
Powered by ViewVC 1.1.20