/[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.5 - (show annotations) (download) (as text)
Tue Oct 7 18:41:09 2003 UTC (11 years, 2 months ago) by swift
Branch: MAIN
Changes since 1.4: +0 -2 lines
File MIME type: application/xml
Fix guide.xsl issues

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

  ViewVC Help
Powered by ViewVC 1.1.20