| 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.7 2004/02/19 15:16:31 swift Exp $ --> |
2 | <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/new-upgrade-to-gentoo-1.4.xml,v 1.8 2004/04/11 10:52:16 cam Exp $ --> |
| 3 | <!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
3 | <!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
| 4 | |
4 | |
| 5 | <guide link="/doc/lang/new-upgrade-to-gentoo-1.4.xml"> |
5 | <guide link="/doc/lang/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> |
| … | |
… | |
| 83 | <p>You will be installing a newer version of GCC during this |
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 |
84 | upgrade. Versions of GCC older than 2.95.3-r8 are not |
| 85 | designed to have multiple versions of GCC installed. You must |
85 | designed to have multiple versions of GCC installed. You must |
| 86 | therefore upgrade GCC to at least version 2.95.3-r8. This |
86 | therefore upgrade GCC to at least version 2.95.3-r8. This |
| 87 | will also have the beneficial side-effect of installing the |
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 |
88 | <c>gcc-config</c> package on your system, which can be used to |
| 89 | switch back and forth between various installed versions of |
89 | switch back and forth between various installed versions of |
| 90 | GCC.</p> |
90 | GCC.</p> |
| 91 | |
91 | |
| 92 | <pre> |
92 | <pre> |
| 93 | # <i>emerge -u gcc</i> |
93 | # <i>emerge -u gcc</i> |
| 94 | </pre> |
94 | </pre> |
| 95 | |
95 | |
| 96 | <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> |
| 97 | <pre> |
97 | <pre> |
| 98 | # <c>gcc-config --get-current-profile</c> |
98 | # <i>gcc-config --get-current-profile</i> |
| 99 | </pre> |
99 | </pre> |
| 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 |
Parent Directory
| 
Revision Log
| 
Patch