| 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> |
| … | |
… | |
| 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> |
| … | |
… | |
| 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> |
|
|
118 | Edit <path>/usr/portage/sys-devel/gcc/gcc-3.2.2.ebuild</path> and search for the |
|
|
119 | line containing <c>DEPEND</c>. Remove the <c>glibc</c> dependency and save the |
|
|
120 | ebuild. |
|
|
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> |
|
|
128 | Now 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> |
Parent Directory
| 
Revision Log
| 
Patch