Gentoo Archives: gentoo-doc-cvs

From: Jan Kundrat <jkt@×××××××××××.org>
To: gentoo-doc-cvs@l.g.o
Subject: [gentoo-doc-cvs] cvs commit: gcc-upgrading.xml
Date: Wed, 13 Sep 2006 14:42:54
Message-Id: 20060913144258.B70DF64788@smtp.gentoo.org
1 jkt 06/09/13 14:42:58
2
3 Modified: gcc-upgrading.xml
4 Log:
5 #146857, don't say "from 3.3 to 3.4 or greater"
6
7 Revision Changes Path
8 1.21 xml/htdocs/doc/en/gcc-upgrading.xml
9
10 file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml?rev=1.21&view=markup
11 plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml?rev=1.21&content-type=text/plain
12 diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml?r1=1.20&r2=1.21
13
14 Index: gcc-upgrading.xml
15 ===================================================================
16 RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v
17 retrieving revision 1.20
18 retrieving revision 1.21
19 diff -u -r1.20 -r1.21
20 --- gcc-upgrading.xml 7 Sep 2006 11:06:40 -0000 1.20
21 +++ gcc-upgrading.xml 13 Sep 2006 14:42:58 -0000 1.21
22 @@ -1,5 +1,5 @@
23 <?xml version='1.0' encoding="UTF-8"?>
24 -<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.20 2006/09/07 11:06:40 rane Exp $ -->
25 +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.21 2006/09/13 14:42:58 jkt Exp $ -->
26
27 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
28
29 @@ -25,8 +25,8 @@
30 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
31 <license/>
32
33 -<version>18</version>
34 -<date>2006-09-06</date>
35 +<version>19</version>
36 +<date>2006-09-13</date>
37
38 <chapter id="intro">
39 <title>Introduction</title>
40 @@ -56,8 +56,8 @@
41 <p>
42 This guide will document the necessary steps required to perform a seamless
43 upgrade of the compiler used by your Gentoo box. A specific section is
44 -dedicated to the <uri link="#upgrade-3.3-to-3.4">upgrade from GCC 3.3 to 3.4 or
45 -greater versions</uri> and issues with <c>libstdc++</c>. A second specific
46 +dedicated to the <uri link="#upgrade-3.3-to-3.4">upgrade from GCC 3.3 to 3.4</uri>
47 +and issues with <c>libstdc++</c>. A second specific
48 section is for users <uri link="#first-install">first installing</uri> Gentoo
49 using a stage3 tarball, after a new GCC major/minor version has been released.
50 </p>
51 @@ -79,8 +79,8 @@
52 <body>
53
54 <impo>
55 -If you're looking for instructions specific to upgrades from GCC-3.3 to GCC-3.4
56 -or greater, please consult the <uri link="#upgrade-3.3-to-3.4">dedicated
57 +If you're looking for instructions specific to upgrades from GCC-3.3 to GCC-3.4,
58 +please consult the <uri link="#upgrade-3.3-to-3.4">dedicated
59 section</uri>.
60 </impo>
61
62 @@ -152,13 +152,13 @@
63 </chapter>
64
65 <chapter id="upgrade-3.3-to-3.4">
66 -<title>Upgrading from GCC-3.3 to 3.4 or greater</title>
67 +<title>Upgrading from GCC-3.3 to 3.4</title>
68 <section>
69 <title>Introduction</title>
70 <body>
71
72 <p>
73 -The upgrade from GCC-3.3 to 3.4 or greater is not seamless as the C++ ABI
74 +The upgrade from GCC-3.3 to 3.4 (or greater) is not seamless as the C++ ABI
75 changed between these two versions. There is an issue with the <c>libstdc++</c>
76 library which must be taken care of, as well.
77 </p>
78 @@ -321,7 +321,7 @@
79 A GCC upgrade on a system after installation from a stage3 tarball is a simple
80 affair. One advantage users of new installations have is they do not have a
81 plethora of software installed that links against the older version of GCC.
82 -The following example is for a GCC-3.3 to 3.4 or greater upgrade. Certain parts
83 +The following example is for a GCC-3.3 to 3.4 upgrade. Certain parts
84 will be different if upgrading from other versions of GCC. For example, the
85 library names used for <c>revdep-rebuild</c> below are GCC 3.3 specific, as
86 well as the need to install <c>libstdc++-v3</c>.
87
88
89
90 --
91 gentoo-doc-cvs@g.o mailing list