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

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

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1.8 - (hide annotations) (download) (as text)
Sun Apr 11 10:52:16 2004 UTC (10 years, 3 months ago) by cam
Branch: MAIN
Changes since 1.7: +2 -2 lines
File MIME type: application/xml
Fixed coding style due to the forthcoming DTD enforcement.
Sorry for all the translators :) (including me, argh)

1 rac 1.1 <?xml version='1.0' encoding="UTF-8"?>
2 cam 1.8 <!-- $Header: /home/cvsroot/gentoo/xml/htdocs/doc/en/new-upgrade-to-gentoo-1.4.xml,v 1.7 2004/02/19 15:16:31 swift Exp $ -->
3 rac 1.1 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
4    
5     <guide link="/doc/lang/new-upgrade-to-gentoo-1.4.xml">
6    
7     <title>Gentoo 1.4 Upgrade Guide</title>
8    
9     <author title = "Author">
10     <mail link = "rac@gentoo.org">Robert Coie</mail>
11     </author>
12    
13     <author title = "Copy Editor">
14     <mail link = "avenj@gentoo.org">Jon Portnoy</mail>
15     </author>
16    
17 swift 1.7 <abstract>A method for upgrading older Gentoo installations in place to Gentoo 1.4</abstract>
18     <license/>
19 rac 1.1 <version>0.1</version>
20     <date>3 March 2003</date>
21    
22 swift 1.4
23 rac 1.1
24     <chapter>
25     <title>Before you begin</title>
26     <section>
27     <title>Be prepared</title>
28     <body>
29     <p>As with any major upgrade to the core of your Gentoo
30     system, there is always the possibility that unforeseen
31     problems will ensue. It is always prudent to back up all
32     important data before beginning this process. If possible,
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
35     machine will need to be recompiled.</p>
36     </body>
37     </section>
38     <section>
39     <title>Other options</title>
40     <body>
41     <p>This is not the only way to upgrade your system. You can
42     install a new 1.4 system onto a separate partition and
43     reuse some of your system configuration instead. This method also has
44     the advantage that you can always go back to your old system
45     in the meantime as a fallback. You may also decide to simply
46     not upgrade your system. If you decide you want to upgrade
47     in place, read on.</p>
48     </body>
49     </section>
50     <section>
51     <title>General notes</title>
52     <body>
53     <p>Whenever the code listings suggest running the
54     <c>emerge</c> command, it is always a good idea to make a test
55     run of the command using the <c>-p</c> or <c>--pretend</c>
56     option to make sure that the command will do what you expect
57     it to do.</p>
58     </body>
59     </section>
60     </chapter>
61     <chapter>
62     <title>Upgrading in place</title>
63     <section>
64     <title>Get Portage as current as possible</title>
65     <body>
66     <p>Some of the syntax of current ebuilds is unreadable by
67     older versions of Portage. If you don't have at least Portage 2.0.44, try upgrading Portage.</p>
68     <pre>
69     # <i>emerge sync</i>
70     # <i>emerge -u portage</i>
71     </pre>
72     <note>If your Portage version is very old, you may get an
73     error message containing the phrase "unscriptable object".
74     Read and follow the instructions in
75     <path>/usr/portage/sys-apps/portage/files/README.RESCUE</path>.
76     Your Portage install should then be
77     current.</note>
78     </body></section>
79    
80     <section>
81     <title>Preparing GCC for cohabitation</title>
82     <body>
83     <p>You will be installing a newer version of GCC during this
84     upgrade. Versions of GCC older than 2.95.3-r8 are not
85     designed to have multiple versions of GCC installed. You must
86     therefore upgrade GCC to at least version 2.95.3-r8. This
87     will also have the beneficial side-effect of installing the
88     <c>gcc-config</c> package on your system, which can be used to
89     switch back and forth between various installed versions of
90     GCC.</p>
91    
92     <pre>
93     # <i>emerge -u gcc</i>
94     </pre>
95    
96     <p>You can now check to see if gcc-config is working properly:</p>
97     <pre>
98 cam 1.8 # <i>gcc-config --get-current-profile</i>
99 rac 1.1 </pre>
100 rac 1.2 <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 rac 1.1 </body>
102     </section>
103     <section>
104     <title>Installing GCC 3</title>
105     <body>
106     <p>Now you can install a newer version of GCC without damaging
107     your current compiler. Look in
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
110     version that is marked stable for your architecture. To see
111     if an ebuild is considered stable for your architecture, look
112     for the KEYWORDS line in the ebuild file. If it has your
113     architecture listed without a ~ in front of it, it is
114     considered stable. Assuming 3.2.2 is the most current stable
115     version, then issue the following command:</p>
116     <pre>
117 rac 1.2 # <i>emerge /usr/portage/sys-devel/gcc/gcc-3.2.2.ebuild</i>
118 rac 1.1 </pre>
119     </body>
120     </section>
121     <section>
122     <title>Changing profiles</title>
123     <body>
124     <p>Now you need to change two sets of profiles: your
125     gcc-config profile and your Portage profile.</p>
126     <pre>
127     # <i>cd /etc</i>
128     # <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>
130     </pre>
131    
132     <pre>
133     # <i>gcc-config --list-profiles</i> <codenote>Note the one for the version you just emerged, use it below</codenote>
134     # <i>gcc-config i686-pc-linux-gnu-3.2.2</i> <codenote>Replace with the version you noted above</codenote>
135     </pre>
136     </body>
137     </section>
138     <section>
139     <title>Recompile toolchain</title>
140     <body>
141     <p>Now you need to recompile your core toolchain with your new
142     compiler. If you are continuing in the same shell, you need
143     to run <c>source /etc/profile</c> as gcc-config instructed you
144     to. Then emerge glibc and binutils using your new
145     compiler:</p>
146     <pre>
147     # <i>emerge glibc binutils</i>
148     </pre>
149     <warn>It is quite likely that you will upgrade glibc from a
150     2.2 or older version to 2.3. Do not downgrade glibc
151     afterwards. Any software you have compiled against glibc 2.3
152     will stop working, and this can make your system
153     unusable.</warn>
154     </body>
155     </section>
156     <section>
157     <title>Recompiling everything with your new compiler</title>
158     <body><p>Now you may recompile everything on your system with
159     your new compiler:</p>
160     <pre>
161     # <i>emerge -e world</i>
162     </pre>
163 rac 1.3 <note>If this command fails at any point due to errors, you
164     can use <c>emerge --resume</c> to continue the process where
165     you left off. This requires Portage 2.0.47 or later.</note>
166 rac 1.1 </body>
167     </section>
168     </chapter>
169     </guide>

  ViewVC Help
Powered by ViewVC 1.1.20