jkt 06/09/13 14:42:58 Modified: gcc-upgrading.xml Log: #146857, don't say "from 3.3 to 3.4 or greater"
Revision Changes Path 1.21 xml/htdocs/doc/en/gcc-upgrading.xml file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml?rev=1.21&view=markup plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml?rev=1.21&content-type=text/plain diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml?r1=1.20&r2=1.21 Index: gcc-upgrading.xml =================================================================== RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v retrieving revision 1.20 retrieving revision 1.21 diff -u -r1.20 -r1.21 --- gcc-upgrading.xml 7 Sep 2006 11:06:40 -0000 1.20 +++ gcc-upgrading.xml 13 Sep 2006 14:42:58 -0000 1.21 @@ -1,5 +1,5 @@ <?xml version='1.0' encoding="UTF-8"?> -<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.20 2006/09/07 11:06:40 rane Exp $ --> +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.21 2006/09/13 14:42:58 jkt Exp $ --> <!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> @@ -25,8 +25,8 @@ <!-- See http://creativecommons.org/licenses/by-sa/2.5 --> <license/> -<version>18</version> -<date>2006-09-06</date> +<version>19</version> +<date>2006-09-13</date> <chapter id="intro"> <title>Introduction</title> @@ -56,8 +56,8 @@ <p> This guide will document the necessary steps required to perform a seamless upgrade of the compiler used by your Gentoo box. A specific section is -dedicated to the <uri link="#upgrade-3.3-to-3.4">upgrade from GCC 3.3 to 3.4 or -greater versions</uri> and issues with <c>libstdc++</c>. A second specific +dedicated to the <uri link="#upgrade-3.3-to-3.4">upgrade from GCC 3.3 to 3.4</uri> +and issues with <c>libstdc++</c>. A second specific section is for users <uri link="#first-install">first installing</uri> Gentoo using a stage3 tarball, after a new GCC major/minor version has been released. </p> @@ -79,8 +79,8 @@ <body> <impo> -If you're looking for instructions specific to upgrades from GCC-3.3 to GCC-3.4 -or greater, please consult the <uri link="#upgrade-3.3-to-3.4">dedicated +If you're looking for instructions specific to upgrades from GCC-3.3 to GCC-3.4, +please consult the <uri link="#upgrade-3.3-to-3.4">dedicated section</uri>. </impo> @@ -152,13 +152,13 @@ </chapter> <chapter id="upgrade-3.3-to-3.4"> -<title>Upgrading from GCC-3.3 to 3.4 or greater</title> +<title>Upgrading from GCC-3.3 to 3.4</title> <section> <title>Introduction</title> <body> <p> -The upgrade from GCC-3.3 to 3.4 or greater is not seamless as the C++ ABI +The upgrade from GCC-3.3 to 3.4 (or greater) is not seamless as the C++ ABI changed between these two versions. There is an issue with the <c>libstdc++</c> library which must be taken care of, as well. </p> @@ -321,7 +321,7 @@ A GCC upgrade on a system after installation from a stage3 tarball is a simple affair. One advantage users of new installations have is they do not have a plethora of software installed that links against the older version of GCC. -The following example is for a GCC-3.3 to 3.4 or greater upgrade. Certain parts +The following example is for a GCC-3.3 to 3.4 upgrade. Certain parts will be different if upgrading from other versions of GCC. For example, the library names used for <c>revdep-rebuild</c> below are GCC 3.3 specific, as well as the need to install <c>libstdc++-v3</c>. -- [email protected] mailing list
