* [gentoo-doc-cvs] cvs commit: gcc-upgrading.xml
@ 2005-12-08 19:21 Jan Kundrat
0 siblings, 0 replies; 27+ messages in thread
From: Jan Kundrat @ 2005-12-08 19:21 UTC (permalink / raw
To: gentoo-doc-cvs
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 11165 bytes --]
jkt 05/12/08 19:21:13
Added: xml/htdocs/doc/en gcc-upgrading.xml
Log:
New generic GCC upgrading guide, replacement of gentoo/xml/htdocs/proj/en/base/x86/gcc-upgrading-guide.xml
Revision Changes Path
1.1 xml/htdocs/doc/en/gcc-upgrading.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gcc-upgrading.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gcc-upgrading.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo
Index: gcc-upgrading.xml
===================================================================
<?xml version='1.0' encoding="UTF-8"?>
<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.1 2005/12/08 19:21:13 jkt Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
<guide link="/doc/en/gcc-upgrading.xml">
<title>Gentoo Linux GCC Upgrade Guide</title>
<author title="Author">
<mail link="amne@gentoo.org">Wernfried Haas</mail>
</author>
<author title="Author">
<mail link="jkt@gentoo.org">Jan Kundrát</mail>
</author>
<author title="Editor">
<mail link="halcy0n@gentoo.org">Mark Loeser</mail>
</author>
<author title="Editor">
<mail link="wolf31o2@gentoo.org">Chris Gianelloni</mail>
</author>
<abstract>
This document will guide the user through the process of upgrading GCC on their
Gentoo Linux machines.
</abstract>
<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
<version>1</version>
<date>2005-12-08</date>
<chapter id="intro">
<title>Introduction</title>
<section>
<title>GCC Upgrading</title>
<body>
<p>
Why should you upgrade? Well, GCC is quite similar to any other package on your
system, just a bit more critical. You should upgrade GCC whenever a new version
fixes some bug that annoys you, new functionality you need is introduced, or if
you want to keep your system up-to-date. If none of the previous cases apply to
you, you can safely postpone upgrade as long as your GCC version is supported by
Gentoo developers.
</p>
<p>
If you install a newer version of GCC, the system will not switch over to use it
automatically. You'll have to explicitly request the change because the
migration process might require some additional steps. If you decide not to
switch, Portage will continue to use older version of your compiler until you
change your mind, or remove the old compiler from the system.
</p>
<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 the 3.4
version</uri> and issues with <c>libstdc++</c>.
</p>
</body>
</section>
</chapter>
<chapter id="upgrade-general">
<title>General Upgrade Instructions</title>
<section>
<title>Introduction</title>
<body>
<impo>
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>
<p>
Generally speaking, upgrades to <e>bug fix releases</e>, like from 3.3.5 to
3.3.6, should be quite safe -- just emerge new version, switch your system to
use it and rebuild the only affected package, <c>libtool</c>. However, some GCC
upgrades break binary compatibility; in such cases a rebuild of the affected
packages (or even whole toolchain and system) might be required.
</p>
<p>
When we spoke about the need to switch your compiler to the newer version by
hand, we said it won't happen automatically. However, there is one exception --
upgrades to bug fix releases, like from 3.3.5 to 3.3.6 in case you don't use the
"multislot" feature allowing them to coexist on one system. Multislot is
disabled by default as the majority of users won't benefit from it.
</p>
<pre caption="Upgrading GCC">
# <i>emerge -uav gcc</i>
<comment>(Please substitute "i686-pc-linux-gnu-3.4.4" with the GCC
version and CHOST settings you've upgraded to:)</comment>
# <i>gcc-config i686-pc-linux-gnu-3.4.4</i>
# <i>source /etc/profile</i>
<comment>(Rebuilding libtool)</comment>
# <i>emerge --oneshot -av libtool</i>
</pre>
<p>
Now let's rebuild toolchain and then world so we will make use of the new
compiler.
</p>
<pre caption="Rebuilding system">
# <i>emerge -eav system</i>
# <i>emerge -eav world</i>
</pre>
<p>
It is safe to remove older GCC version at this time. If you feel the
need, please issue the following command (as usual, substitute
<c>=sys-devel/gcc-3.3*</c> with the version you want to uninstall):
</p>
<pre caption="Removing older GCC version">
# <i>emerge -aC =sys-devel/gcc-3.3*</i>
</pre>
</body>
</section>
</chapter>
<chapter id="upgrade-3.3-to-3.4">
<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 is not so seamless as the C++ ABI changed
between these two versions so there is an issue with <c>libstdc++</c> library
which must be taken care of as well.
</p>
</body>
</section>
<section id="upgrade-3.3-to-3.4-choices">
<title>The Choices</title>
<body>
<p>
You have two possibilities on how to upgrade your system. <uri
link="#upgrade-3.3-to-3.4-revdep-rebuild">First method</uri> is faster and
requires use of <c>revdep-rebuild</c> tool from package <c>gentoolkit</c> while
the <uri link="#upgrade-3.3-to-3.4-emerge-e">second one</uri> rebuilds the
entire system from scratch so it will make use of new GCC features. It's up to
you to decide which of these two ways you will choose.
</p>
</body>
</section>
<section id="upgrade-3.3-to-3.4-revdep-rebuild">
<title>Using revdep-rebuild</title>
<body>
<p>
This method requires that you first install <c>gentoolkit</c> if you have not
already done so. Then we will upgrade GCC and switch to the new compiler. We
will also rebuild the <c>libtool</c> package to ensurethat toolchain is in
healthy state.
</p>
<pre caption="Installing gentoolkit and upgrading GCC">
# <i>emerge -an gentoolkit</i>
# <i>emerge -uav gcc</i>
# <i>gcc-config i686-pc-linux-gnu-3.4.4</i>
# <i>source /etc/profile</i>
<comment>(Rebuilding libtool)</comment>
# <i>emerge --oneshot -av libtool</i>
</pre>
<note>
This assumes that you have <c>CHOST="i686-pc-linux-gnu"</c> set. If you are
using another CHOST, please use the appropriate gcc-config line.
</note>
<p>
Now, we want to see which packages that revdep-rebuild will want to rebuild.
Then we will tell revdep-rebuild to actually rebuild the packages. This may take
some time, so have some patience.
</p>
<pre caption="Using revdep-rebuild">
# <i>revdep-rebuild --library libstdc++.so.5 -- -p -v</i>
# <i>revdep-rebuild --library libstdc++.so.5</i>
</pre>
<note>
It is possible that you might have problems with non-existing package versions
due to them being outdated or masked. If this is the case, you will want to use
the <c>--package-names</c> option to <c>revdep-rebuild</c>. This causes packages
to be recompiled based on the package name, rather than the exact name and
version.
</note>
<p>
To provide compatibility with older binary C++ applications and any packages
that revdep-rebuild might have missed, <c>sys-libs/libstdc++-v3</c> needs to be
merged before you unmerge GCC 3.3 from your system.
</p>
<pre caption="Installing libstdc++-v3 and cleaning up">
# <i>emerge --oneshot sys-libs/libstdc++-v3</i>
# <i>emerge -aC =sys-devel/gcc-3.3*</i>
</pre>
</body>
</section>
<section id="upgrade-3.3-to-3.4-emerge-e">
<title>Using emerge -e</title>
<body>
<p>
This method, while much slower, will rebuild your whole system to ensure that
everything has been rebuilt with your new compiler, and therefore safer. At
first, you will upgrade GCC and libtool and switch to your new compiler.
</p>
<pre caption="Upgrading GCC">
# <i>emerge -uav gcc</i>
# <i>gcc-config i686-pc-linux-gnu-3.4.4</i>
# <i>source /etc/profile</i>
<comment>(Rebuilding libtool)</comment>
# <i>emerge --oneshot -av libtool</i>
</pre>
<note>
This assumes that you have <c>CHOST="i686-pc-linux-gnu"</c> set. If you are
using another CHOST, please use the appropriate gcc-config line.
</note>
<p>
To provide compatibility with older binary C++ applications,
<c>sys-libs/libstdc++-v3</c> needs to be merged onto your system.
</p>
<pre caption="Installing libstdc++-v3">
# <i>emerge --oneshot sys-libs/libstdc++-v3</i>
</pre>
<p>
Now we will go about first rebuilding the system target, then the world target.
This will take a very long time, depending on the number of packages that you
have installed, as it will rebuild your entire toolchain and supporting system
files, followed by every package on your system, including the toolchain. This
is necessary to ensure that all packages have been compiled with the new
toolchain, including the toolchain itself.
</p>
<pre caption="Rebuilding system and world">
# <i>emerge -e system</i>
# <i>emerge -e world</i>
</pre>
<p>
It is also safe to remove older GCC versions at this time:
</p>
<pre caption="Cleaning up">
# <i>emerge -aC =sys-devel/gcc-3.3*</i>
</pre>
</body>
</section>
</chapter>
<chapter id="common-pittfalls">
<title>Common Pittfalls</title>
<section>
<body>
<p>
It's important to disable <c>distcc</c> during upgrade. Mixing compiler versions
on your nodes <e>will</e> cause build issues. This is not required for ccache,
as the cache objects will be invalidated anyway.
</p>
<p>
Always use same GCC version for your kernel and additional kernel modules. Once
you rebuild your world with new GCC, external modules (like
<c>app-emulation/qemu-softmmu</c>) will fail to load. Please rebuild your kernel
with new GCC to fix that.
</p>
</body>
</section>
<section>
<title>Frequent Error Messages</title>
<body>
<p>
If your system complains about something like <e>libtool: link:
`/usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.6/libstdc++.la' is not a valid libtool
archive</e>, please run <c>/sbin/fix_libtool_files.sh 3.3.6</c> (substitute
"3.3.6" with the version numbers from the error message).
</p>
<p>
If you see the <e>error: /usr/bin/gcc-config: line 632:
/etc/env.d/gcc/i686-pc-linux-gnu-3.3.5: No such file or directory</e>, then try
deleting <path>/etc/env.d/gcc/config-i686-pc-linux-gnu</path> and running
<c>gcc-config</c> again, followed by <c>source /etc/profile</c>. Only do this if
you do not have any cross-compilers set up, though.
</p>
<p>
If a package fails during <c>emerge -e system/world</c>, you can resume
operation with <c>emerge --resume</c>. If a package fails repeatedly, skip it
with <c>emerge --resume --skipfirst</c>. Don't run any other instances of emerge
in between or you will lose the resume information.
</p>
<p>
If you get an error message <e>spec failure: unrecognized spec option</e> while
upgrading your compiler, try to switch back to your default compiler, unset the
<c>GCC_SPECS</c> variable and upgrade GCC again:
</p>
<pre caption="Restoring primary specs">
# <i>gcc-config 1</i>
# <i>source /etc/profile</i>
# <i>unset GCC_SPECS</i>
# <i>emerge -uav gcc</i>
</pre>
</body>
</section>
</chapter>
</guide>
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 27+ messages in thread
* [gentoo-doc-cvs] cvs commit: gcc-upgrading.xml
@ 2005-12-08 19:25 Jan Kundrat
0 siblings, 0 replies; 27+ messages in thread
From: Jan Kundrat @ 2005-12-08 19:25 UTC (permalink / raw
To: gentoo-doc-cvs
jkt 05/12/08 19:25:55
Modified: xml/htdocs/doc/en gcc-upgrading.xml
Log:
"pitfall", not "pittfall"... but ispell missed that :-)
Revision Changes Path
1.2 +4 -4 xml/htdocs/doc/en/gcc-upgrading.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gcc-upgrading.xml?rev=1.2&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gcc-upgrading.xml?rev=1.2&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gcc-upgrading.xml.diff?r1=1.1&r2=1.2&cvsroot=gentoo
Index: gcc-upgrading.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- gcc-upgrading.xml 8 Dec 2005 19:21:13 -0000 1.1
+++ gcc-upgrading.xml 8 Dec 2005 19:25:55 -0000 1.2
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.1 2005/12/08 19:21:13 jkt Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.2 2005/12/08 19:25:55 jkt Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -29,7 +29,7 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>1</version>
+<version>2</version>
<date>2005-12-08</date>
<chapter id="intro">
@@ -276,8 +276,8 @@
</section>
</chapter>
-<chapter id="common-pittfalls">
-<title>Common Pittfalls</title>
+<chapter id="common-pitfalls">
+<title>Common Pitfalls</title>
<section>
<body>
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 27+ messages in thread
* [gentoo-doc-cvs] cvs commit: gcc-upgrading.xml
@ 2005-12-12 15:41 Jan Kundrat
0 siblings, 0 replies; 27+ messages in thread
From: Jan Kundrat @ 2005-12-12 15:41 UTC (permalink / raw
To: gentoo-doc-cvs
jkt 05/12/12 15:41:26
Modified: xml/htdocs/doc/en gcc-upgrading.xml
Log:
16:37 < Halcy0n> You are missing a space :)
Revision Changes Path
1.3 +2 -2 xml/htdocs/doc/en/gcc-upgrading.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gcc-upgrading.xml?rev=1.3&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gcc-upgrading.xml?rev=1.3&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gcc-upgrading.xml.diff?r1=1.2&r2=1.3&cvsroot=gentoo
Index: gcc-upgrading.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- gcc-upgrading.xml 8 Dec 2005 19:25:55 -0000 1.2
+++ gcc-upgrading.xml 12 Dec 2005 15:41:26 -0000 1.3
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.2 2005/12/08 19:25:55 jkt Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.3 2005/12/12 15:41:26 jkt Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -166,7 +166,7 @@
<p>
This method requires that you first install <c>gentoolkit</c> if you have not
already done so. Then we will upgrade GCC and switch to the new compiler. We
-will also rebuild the <c>libtool</c> package to ensurethat toolchain is in
+will also rebuild the <c>libtool</c> package to ensure that toolchain is in
healthy state.
</p>
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 27+ messages in thread
* [gentoo-doc-cvs] cvs commit: gcc-upgrading.xml
@ 2005-12-14 20:03 Jan Kundrat
0 siblings, 0 replies; 27+ messages in thread
From: Jan Kundrat @ 2005-12-14 20:03 UTC (permalink / raw
To: gentoo-doc-cvs
jkt 05/12/14 20:03:44
Modified: xml/htdocs/doc/en gcc-upgrading.xml
Log:
Removing wolf31o2 per his request
Revision Changes Path
1.4 +2 -5 xml/htdocs/doc/en/gcc-upgrading.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gcc-upgrading.xml?rev=1.4&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gcc-upgrading.xml?rev=1.4&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gcc-upgrading.xml.diff?r1=1.3&r2=1.4&cvsroot=gentoo
Index: gcc-upgrading.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- gcc-upgrading.xml 12 Dec 2005 15:41:26 -0000 1.3
+++ gcc-upgrading.xml 14 Dec 2005 20:03:44 -0000 1.4
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.3 2005/12/12 15:41:26 jkt Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.4 2005/12/14 20:03:44 jkt Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -15,9 +15,6 @@
<author title="Editor">
<mail link="halcy0n@gentoo.org">Mark Loeser</mail>
</author>
-<author title="Editor">
- <mail link="wolf31o2@gentoo.org">Chris Gianelloni</mail>
-</author>
<abstract>
@@ -29,7 +26,7 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>2</version>
+<version>3</version>
<date>2005-12-08</date>
<chapter id="intro">
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 27+ messages in thread
* [gentoo-doc-cvs] cvs commit: gcc-upgrading.xml
@ 2006-01-30 15:32 Jan Kundrat
0 siblings, 0 replies; 27+ messages in thread
From: Jan Kundrat @ 2006-01-30 15:32 UTC (permalink / raw
To: gentoo-doc-cvs
jkt 06/01/30 15:32:52
Modified: xml/htdocs/doc/en gcc-upgrading.xml
Log:
#120164: add a warning about migrating from 3.3 to 3.4 on SPARC
Revision Changes Path
1.5 +10 -3 xml/htdocs/doc/en/gcc-upgrading.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gcc-upgrading.xml?rev=1.5&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gcc-upgrading.xml?rev=1.5&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gcc-upgrading.xml.diff?r1=1.4&r2=1.5&cvsroot=gentoo
Index: gcc-upgrading.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- gcc-upgrading.xml 14 Dec 2005 20:03:44 -0000 1.4
+++ gcc-upgrading.xml 30 Jan 2006 15:32:52 -0000 1.5
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.4 2005/12/14 20:03:44 jkt Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.5 2006/01/30 15:32:52 jkt Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -26,8 +26,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>3</version>
-<date>2005-12-08</date>
+<version>4</version>
+<date>2006-01-30</date>
<chapter id="intro">
<title>Introduction</title>
@@ -145,6 +145,13 @@
<title>The Choices</title>
<body>
+<impo>
+If you're upgrading on a SPARC machine, you will have to take the way of
+<uri link="#upgrade-3.3-to-3.4-emerge-e">complete system rebuild</uri> due to
+some internal <uri link="http://gcc.gnu.org/gcc-3.4/sparc-abi.html">ABI
+changes</uri> in GCC's parameter passing.
+</impo>
+
<p>
You have two possibilities on how to upgrade your system. <uri
link="#upgrade-3.3-to-3.4-revdep-rebuild">First method</uri> is faster and
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 27+ messages in thread
* [gentoo-doc-cvs] cvs commit: gcc-upgrading.xml
@ 2006-02-02 15:59 Xavier Neys
0 siblings, 0 replies; 27+ messages in thread
From: Xavier Neys @ 2006-02-02 15:59 UTC (permalink / raw
To: gentoo-doc-cvs
neysx 06/02/02 15:59:29
Modified: xml/htdocs/doc/en gcc-upgrading.xml
Log:
#121306 GCC Upgrade Guide enchancements
Revision Changes Path
1.6 +185 -24 xml/htdocs/doc/en/gcc-upgrading.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gcc-upgrading.xml?rev=1.6&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gcc-upgrading.xml?rev=1.6&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gcc-upgrading.xml.diff?r1=1.5&r2=1.6&cvsroot=gentoo
Index: gcc-upgrading.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- gcc-upgrading.xml 30 Jan 2006 15:32:52 -0000 1.5
+++ gcc-upgrading.xml 2 Feb 2006 15:59:29 -0000 1.6
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.5 2006/01/30 15:32:52 jkt Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.6 2006/02/02 15:59:29 neysx Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -16,7 +16,6 @@
<mail link="halcy0n@gentoo.org">Mark Loeser</mail>
</author>
-
<abstract>
This document will guide the user through the process of upgrading GCC on their
Gentoo Linux machines.
@@ -26,8 +25,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>4</version>
-<date>2006-01-30</date>
+<version>5</version>
+<date>2006-02-02</date>
<chapter id="intro">
<title>Introduction</title>
@@ -54,11 +53,20 @@
<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 the 3.4
-version</uri> and issues with <c>libstdc++</c>.
+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
+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>
+<note>
+It should be noted that upgrading from GCC-3.4 to GCC-4.0 or greater requires
+no real changes to be made by the user, as GCC-3.4 and GCC-4.0 use the same
+ABI. All that is required is that <c>gcc-config</c> is used to select the
+compiler desired.
+</note>
+
</body>
</section>
</chapter>
@@ -70,8 +78,14 @@
<body>
<impo>
-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
+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
+section</uri>.
+</impo>
+
+<impo>
+If you're looking for instructions specific to upgrades in GCC for new
+installs, please consult the <uri link="#first-install">dedicated
section</uri>.
</impo>
@@ -114,8 +128,8 @@
</pre>
<p>
-It is safe to remove older GCC version at this time. If you feel the
-need, please issue the following command (as usual, substitute
+It is safe to remove the older GCC version at this time. If you feel the need,
+please issue the following command (as usual, substitute
<c>=sys-devel/gcc-3.3*</c> with the version you want to uninstall):
</p>
@@ -128,15 +142,15 @@
</chapter>
<chapter id="upgrade-3.3-to-3.4">
-<title>Upgrading from GCC-3.3 to 3.4</title>
+<title>Upgrading from GCC-3.3 to 3.4 or greater</title>
<section>
<title>Introduction</title>
<body>
<p>
-The upgrade from GCC/3.3 to 3.4 is not so seamless as the C++ ABI changed
-between these two versions so there is an issue with <c>libstdc++</c> library
-which must be taken care of as well.
+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>
</body>
@@ -153,12 +167,13 @@
</impo>
<p>
-You have two possibilities on how to upgrade your system. <uri
-link="#upgrade-3.3-to-3.4-revdep-rebuild">First method</uri> is faster and
-requires use of <c>revdep-rebuild</c> tool from package <c>gentoolkit</c> while
-the <uri link="#upgrade-3.3-to-3.4-emerge-e">second one</uri> rebuilds the
+You have two possibilities on how to upgrade your system. The <uri
+link="#upgrade-3.3-to-3.4-revdep-rebuild">first method</uri> is faster and
+requires use of the <c>revdep-rebuild</c> tool from package <c>gentoolkit</c>
+while the <uri link="#upgrade-3.3-to-3.4-emerge-e">second one</uri> rebuilds the
entire system from scratch so it will make use of new GCC features. It's up to
-you to decide which of these two ways you will choose.
+you to decide which of these two ways you will choose. In most cases, the first
+method is sufficient.
</p>
</body>
@@ -320,10 +335,10 @@
</p>
<p>
-If a package fails during <c>emerge -e system/world</c>, you can resume
-operation with <c>emerge --resume</c>. If a package fails repeatedly, skip it
-with <c>emerge --resume --skipfirst</c>. Don't run any other instances of emerge
-in between or you will lose the resume information.
+If a package fails during <c>emerge -e system</c> or <c>emerge -e world</c>,
+you can resume operation with <c>emerge --resume</c>. If a package fails
+repeatedly, skip it with <c>emerge --resume --skipfirst</c>. Don't run any
+other instances of emerge in between or you will lose the resume information.
</p>
<p>
@@ -341,6 +356,152 @@
</body>
</section>
+</chapter>
+
+<chapter id="first-install">
+<title>Upgrading to GCC on a First Install</title>
+<section>
+<title>Introduction</title>
+<body>
+
+<p>
+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
+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>.
+</p>
+
+<p>
+If a user has not made any customizations to their system yet, then there are
+very few steps to get their system upgraded to a new GCC version. As with the
+GCC-3.3 to 3.4 upgrade, the user has a couple options. However, unlike the
+GCC-3.3 to 3.4 upgrade, this one is less complicated as there are fewer
+differences between the methods. The <uri
+link="#first-install-revdep-rebuild">first method</uri> is faster and makes use
+of the <c>revdep-rebuild</c> tool from <c>gentoolkit</c>, similar to the above
+procedure. Using revdep-rebuild causes only packages which actually link
+against GCC libraries to be rebuilt, while the <uri
+link="#first-install-emerge-e">second method</uri> causes your entire new
+install to be recompiled with the new GCC version and takes much longer. This
+second method is never required and only documented for completeness.
+</p>
+
+<p>
+These first steps are common between both methods, and should be completed by
+everyone.
+</p>
+
+<pre caption="Upgrading GCC">
+# <i>emerge -uav gcc</i>
+# <i>gcc-config i686-pc-linux-gnu-3.4.4</i>
+# <i>source /etc/profile</i>
+
+<comment>(Rebuilding libtool)</comment>
+# <i>emerge --oneshot -av libtool</i>
+</pre>
+
+<note>
+This assumes that you have <c>CHOST="i686-pc-linux-gnu"</c> set. If you are
+using another CHOST, please use the appropriate gcc-config line.
+</note>
+
+<p>
+To provide compatibility with older binary C++ applications,
+<c>sys-libs/libstdc++-v3</c> needs to be merged onto your system.
+</p>
+
+<pre caption="Installing libstdc++-v3">
+# <i>emerge --oneshot sys-libs/libstdc++-v3</i>
+</pre>
+
+</body>
+</section>
+
+<section id="first-install-revdep-rebuild">
+<title>Using revdep-rebuild</title>
+<body>
+
+<p>
+This method requires that you first install <c>gentoolkit</c> if you have not
+already done so. We will then run <c>revdep-rebuild</c> to actually scan the
+installed packages for ones we need to rebuild, then rebuild them.
+</p>
+
+<pre caption="Installing gentoolkit and running revdep-rebuild">
+# <i>emerge -an gentoolkit</i>
+# <i>revdep-rebuild --library libstdc++.so.5 -- -p -v</i>
+# <i>revdep-rebuild --library libstdc++.so.5</i>
+</pre>
+
+<note>
+It is possible that you might have problems with non-existing package versions
+due to them being outdated or masked. If this is the case, you will want to use
+the <c>--package-names</c> option to <c>revdep-rebuild</c>. This causes packages
+to be recompiled based on the package name, rather than the exact name and
+version.
+</note>
+
+</body>
+</section>
+<section id="first-install-emerge-e">
+<title>Using emerge -e</title>
+<body>
+
+<p>
+This method, while much slower, will rebuild the system target to ensure that
+everything has been rebuilt with your new compiler. This is not necessary, but
+is valid if you are also making changes to CFLAGS or other make.conf variables
+that will affect the system compile.
+</p>
+
+<pre caption="Upgrading GCC">
+# <i>emerge -uav gcc</i>
+# <i>gcc-config i686-pc-linux-gnu-3.4.4</i>
+# <i>source /etc/profile</i>
+<comment>(Rebuilding libtool)</comment>
+# <i>emerge --oneshot -av libtool</i>
+</pre>
+
+<note>
+This assumes that you have <c>CHOST="i686-pc-linux-gnu"</c> set. If you are
+using another CHOST, please use the appropriate gcc-config line.
+</note>
+
+<p>
+To provide compatibility with older binary C++ applications,
+<c>sys-libs/libstdc++-v3</c> needs to be merged onto your system.
+</p>
+
+<pre caption="Installing libstdc++-v3">
+# <i>emerge --oneshot sys-libs/libstdc++-v3</i>
+</pre>
+
+<p>
+Since we are performing these actions after an initial installation, we do not
+need to recompile the world target as we would when doing an upgrade on an
+already installed system. However, you may choose to perform a world update in
+place of the system update, to ensure that all packages are updated.
+</p>
+
+<pre caption="Rebuilding system">
+# <i>emerge -e system</i>
+</pre>
+
+<p>
+It is also safe to remove older GCC versions at this time. Since this is an
+initial installation, we are using portage's prune feature to remove all older
+versions of GCC.
+</p>
+
+<pre caption="Cleaning up">
+# <i>emerge -aP sys-devel/gcc</i>
+</pre>
+
+</body>
+</section>
</chapter>
</guide>
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 27+ messages in thread
* [gentoo-doc-cvs] cvs commit: gcc-upgrading.xml
@ 2006-02-09 16:06 Jan Kundrat
0 siblings, 0 replies; 27+ messages in thread
From: Jan Kundrat @ 2006-02-09 16:06 UTC (permalink / raw
To: gentoo-doc-cvs
jkt 06/02/09 16:06:51
Modified: xml/htdocs/doc/en gcc-upgrading.xml
Log:
Better command to prune the old GCC version for fresh installations.
Thanks to bdillahu for reporting and Halcy0n for a fix :)
Revision Changes Path
1.7 +6 -7 xml/htdocs/doc/en/gcc-upgrading.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gcc-upgrading.xml?rev=1.7&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gcc-upgrading.xml?rev=1.7&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gcc-upgrading.xml.diff?r1=1.6&r2=1.7&cvsroot=gentoo
Index: gcc-upgrading.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- gcc-upgrading.xml 2 Feb 2006 15:59:29 -0000 1.6
+++ gcc-upgrading.xml 9 Feb 2006 16:06:51 -0000 1.7
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.6 2006/02/02 15:59:29 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.7 2006/02/09 16:06:51 jkt Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -25,8 +25,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>5</version>
-<date>2006-02-02</date>
+<version>6</version>
+<date>2006-02-09</date>
<chapter id="intro">
<title>Introduction</title>
@@ -492,13 +492,12 @@
</pre>
<p>
-It is also safe to remove older GCC versions at this time. Since this is an
-initial installation, we are using portage's prune feature to remove all older
-versions of GCC.
+It is also safe to remove older GCC versions at this time. Please substitute
+<c>YOUR-NEW-GCC-VERSION</c> with the actual version you've upgraded to:
</p>
<pre caption="Cleaning up">
-# <i>emerge -aP sys-devel/gcc</i>
+# <i>emerge -aC "<sys-devel/gcc-YOUR-NEW-GCC-VERSION"</i>
</pre>
</body>
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 27+ messages in thread
* [gentoo-doc-cvs] cvs commit: gcc-upgrading.xml
@ 2006-02-09 16:15 Jan Kundrat
0 siblings, 0 replies; 27+ messages in thread
From: Jan Kundrat @ 2006-02-09 16:15 UTC (permalink / raw
To: gentoo-doc-cvs
jkt 06/02/09 16:15:21
Modified: xml/htdocs/doc/en gcc-upgrading.xml
Log:
Moving the "common-pitfalls" section to the end of the document
Revision Changes Path
1.8 +65 -65 xml/htdocs/doc/en/gcc-upgrading.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gcc-upgrading.xml?rev=1.8&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gcc-upgrading.xml?rev=1.8&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gcc-upgrading.xml.diff?r1=1.7&r2=1.8&cvsroot=gentoo
Index: gcc-upgrading.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- gcc-upgrading.xml 9 Feb 2006 16:06:51 -0000 1.7
+++ gcc-upgrading.xml 9 Feb 2006 16:15:21 -0000 1.8
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.7 2006/02/09 16:06:51 jkt Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.8 2006/02/09 16:15:21 jkt Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -25,7 +25,7 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>6</version>
+<version>7</version>
<date>2006-02-09</date>
<chapter id="intro">
@@ -295,69 +295,6 @@
</section>
</chapter>
-<chapter id="common-pitfalls">
-<title>Common Pitfalls</title>
-<section>
-<body>
-
-<p>
-It's important to disable <c>distcc</c> during upgrade. Mixing compiler versions
-on your nodes <e>will</e> cause build issues. This is not required for ccache,
-as the cache objects will be invalidated anyway.
-</p>
-
-<p>
-Always use same GCC version for your kernel and additional kernel modules. Once
-you rebuild your world with new GCC, external modules (like
-<c>app-emulation/qemu-softmmu</c>) will fail to load. Please rebuild your kernel
-with new GCC to fix that.
-</p>
-
-</body>
-</section>
-<section>
-<title>Frequent Error Messages</title>
-<body>
-
-<p>
-If your system complains about something like <e>libtool: link:
-`/usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.6/libstdc++.la' is not a valid libtool
-archive</e>, please run <c>/sbin/fix_libtool_files.sh 3.3.6</c> (substitute
-"3.3.6" with the version numbers from the error message).
-</p>
-
-<p>
-If you see the <e>error: /usr/bin/gcc-config: line 632:
-/etc/env.d/gcc/i686-pc-linux-gnu-3.3.5: No such file or directory</e>, then try
-deleting <path>/etc/env.d/gcc/config-i686-pc-linux-gnu</path> and running
-<c>gcc-config</c> again, followed by <c>source /etc/profile</c>. Only do this if
-you do not have any cross-compilers set up, though.
-</p>
-
-<p>
-If a package fails during <c>emerge -e system</c> or <c>emerge -e world</c>,
-you can resume operation with <c>emerge --resume</c>. If a package fails
-repeatedly, skip it with <c>emerge --resume --skipfirst</c>. Don't run any
-other instances of emerge in between or you will lose the resume information.
-</p>
-
-<p>
-If you get an error message <e>spec failure: unrecognized spec option</e> while
-upgrading your compiler, try to switch back to your default compiler, unset the
-<c>GCC_SPECS</c> variable and upgrade GCC again:
-</p>
-
-<pre caption="Restoring primary specs">
-# <i>gcc-config 1</i>
-# <i>source /etc/profile</i>
-# <i>unset GCC_SPECS</i>
-# <i>emerge -uav gcc</i>
-</pre>
-
-</body>
-</section>
-</chapter>
-
<chapter id="first-install">
<title>Upgrading to GCC on a First Install</title>
<section>
@@ -503,4 +440,67 @@
</body>
</section>
</chapter>
+
+<chapter id="common-pitfalls">
+<title>Common Pitfalls</title>
+<section>
+<body>
+
+<p>
+It's important to disable <c>distcc</c> during upgrade. Mixing compiler versions
+on your nodes <e>will</e> cause build issues. This is not required for ccache,
+as the cache objects will be invalidated anyway.
+</p>
+
+<p>
+Always use same GCC version for your kernel and additional kernel modules. Once
+you rebuild your world with new GCC, external modules (like
+<c>app-emulation/qemu-softmmu</c>) will fail to load. Please rebuild your kernel
+with new GCC to fix that.
+</p>
+
+</body>
+</section>
+<section>
+<title>Frequent Error Messages</title>
+<body>
+
+<p>
+If your system complains about something like <e>libtool: link:
+`/usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.6/libstdc++.la' is not a valid libtool
+archive</e>, please run <c>/sbin/fix_libtool_files.sh 3.3.6</c> (substitute
+"3.3.6" with the version numbers from the error message).
+</p>
+
+<p>
+If you see the <e>error: /usr/bin/gcc-config: line 632:
+/etc/env.d/gcc/i686-pc-linux-gnu-3.3.5: No such file or directory</e>, then try
+deleting <path>/etc/env.d/gcc/config-i686-pc-linux-gnu</path> and running
+<c>gcc-config</c> again, followed by <c>source /etc/profile</c>. Only do this if
+you do not have any cross-compilers set up, though.
+</p>
+
+<p>
+If a package fails during <c>emerge -e system</c> or <c>emerge -e world</c>,
+you can resume operation with <c>emerge --resume</c>. If a package fails
+repeatedly, skip it with <c>emerge --resume --skipfirst</c>. Don't run any
+other instances of emerge in between or you will lose the resume information.
+</p>
+
+<p>
+If you get an error message <e>spec failure: unrecognized spec option</e> while
+upgrading your compiler, try to switch back to your default compiler, unset the
+<c>GCC_SPECS</c> variable and upgrade GCC again:
+</p>
+
+<pre caption="Restoring primary specs">
+# <i>gcc-config 1</i>
+# <i>source /etc/profile</i>
+# <i>unset GCC_SPECS</i>
+# <i>emerge -uav gcc</i>
+</pre>
+
+</body>
+</section>
+</chapter>
</guide>
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 27+ messages in thread
* [gentoo-doc-cvs] cvs commit: gcc-upgrading.xml
@ 2006-02-09 17:40 Jan Kundrat
0 siblings, 0 replies; 27+ messages in thread
From: Jan Kundrat @ 2006-02-09 17:40 UTC (permalink / raw
To: gentoo-doc-cvs
jkt 06/02/09 17:40:19
Modified: xml/htdocs/doc/en gcc-upgrading.xml
Log:
#120164, mention the need to re-run SILO
Revision Changes Path
1.9 +7 -2 xml/htdocs/doc/en/gcc-upgrading.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gcc-upgrading.xml?rev=1.9&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gcc-upgrading.xml?rev=1.9&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gcc-upgrading.xml.diff?r1=1.8&r2=1.9&cvsroot=gentoo
Index: gcc-upgrading.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- gcc-upgrading.xml 9 Feb 2006 16:15:21 -0000 1.8
+++ gcc-upgrading.xml 9 Feb 2006 17:40:19 -0000 1.9
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.8 2006/02/09 16:15:21 jkt Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.9 2006/02/09 17:40:19 jkt Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -25,7 +25,7 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>7</version>
+<version>8</version>
<date>2006-02-09</date>
<chapter id="intro">
@@ -459,6 +459,11 @@
with new GCC to fix that.
</p>
+<p>
+If you're upgrading on a SPARC machine, make sure to rerun <c>silo -f</c> after
+re-emerging world to avoid possible issues.
+</p>
+
</body>
</section>
<section>
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 27+ messages in thread
* [gentoo-doc-cvs] cvs commit: gcc-upgrading.xml
@ 2006-02-25 9:37 Jan Kundrat
0 siblings, 0 replies; 27+ messages in thread
From: Jan Kundrat @ 2006-02-25 9:37 UTC (permalink / raw
To: gentoo-doc-cvs
jkt 06/02/25 09:37:34
Modified: xml/htdocs/doc/en gcc-upgrading.xml
Log:
a) removed redundant instructions for first time installations
b) added <c> around the "world" target
c) moved the "remove old gcc" instructions for first-time installations
to separate <section> as it's safe even for the revdep-rebuild way
Revision Changes Path
1.10 +12 -29 xml/htdocs/doc/en/gcc-upgrading.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gcc-upgrading.xml?rev=1.10&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gcc-upgrading.xml?rev=1.10&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gcc-upgrading.xml.diff?r1=1.9&r2=1.10&cvsroot=gentoo
Index: gcc-upgrading.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- gcc-upgrading.xml 9 Feb 2006 17:40:19 -0000 1.9
+++ gcc-upgrading.xml 25 Feb 2006 09:37:33 -0000 1.10
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.9 2006/02/09 17:40:19 jkt Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.10 2006/02/25 09:37:33 jkt Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -25,8 +25,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>8</version>
-<date>2006-02-09</date>
+<version>9</version>
+<date>2006-02-25</date>
<chapter id="intro">
<title>Introduction</title>
@@ -394,40 +394,23 @@
that will affect the system compile.
</p>
-<pre caption="Upgrading GCC">
-# <i>emerge -uav gcc</i>
-# <i>gcc-config i686-pc-linux-gnu-3.4.4</i>
-# <i>source /etc/profile</i>
-
-<comment>(Rebuilding libtool)</comment>
-# <i>emerge --oneshot -av libtool</i>
-</pre>
-
-<note>
-This assumes that you have <c>CHOST="i686-pc-linux-gnu"</c> set. If you are
-using another CHOST, please use the appropriate gcc-config line.
-</note>
-
-<p>
-To provide compatibility with older binary C++ applications,
-<c>sys-libs/libstdc++-v3</c> needs to be merged onto your system.
-</p>
-
-<pre caption="Installing libstdc++-v3">
-# <i>emerge --oneshot sys-libs/libstdc++-v3</i>
-</pre>
-
<p>
Since we are performing these actions after an initial installation, we do not
-need to recompile the world target as we would when doing an upgrade on an
-already installed system. However, you may choose to perform a world update in
-place of the system update, to ensure that all packages are updated.
+need to recompile the <c>world</c> target as we would when doing an upgrade on
+an already installed system. However, you may choose to perform a world update
+in place of the system update, to ensure that all packages are updated.
</p>
<pre caption="Rebuilding system">
# <i>emerge -e system</i>
</pre>
+</body>
+</section>
+<section id="first-install-cleaning-up">
+<title>Cleaning up</title>
+<body>
+
<p>
It is also safe to remove older GCC versions at this time. Please substitute
<c>YOUR-NEW-GCC-VERSION</c> with the actual version you've upgraded to:
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 27+ messages in thread
* [gentoo-doc-cvs] cvs commit: gcc-upgrading.xml
@ 2006-03-01 1:54 Marcelo Goes
0 siblings, 0 replies; 27+ messages in thread
From: Marcelo Goes @ 2006-03-01 1:54 UTC (permalink / raw
To: gentoo-doc-cvs
vanquirius 06/03/01 01:54:04
Modified: xml/htdocs/doc/en gcc-upgrading.xml
Log:
3.4.4->3.4.5, add "(Please substitute "i686-pc-linux-gnu-3.4.5" with the GCC
version and CHOST settings you've upgraded to:)" to all codelists that
have gcc-config in them. Reported by Justin R Eylander
<jeylande at cs dot indiana dot edu> via e-mail.
Revision Changes Path
1.11 +14 -8 xml/htdocs/doc/en/gcc-upgrading.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gcc-upgrading.xml?rev=1.11&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gcc-upgrading.xml?rev=1.11&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gcc-upgrading.xml.diff?r1=1.10&r2=1.11&cvsroot=gentoo
Index: gcc-upgrading.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- gcc-upgrading.xml 25 Feb 2006 09:37:33 -0000 1.10
+++ gcc-upgrading.xml 1 Mar 2006 01:54:04 -0000 1.11
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.10 2006/02/25 09:37:33 jkt Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.11 2006/03/01 01:54:04 vanquirius Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -25,8 +25,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>9</version>
-<date>2006-02-25</date>
+<version>10</version>
+<date>2006-02-28</date>
<chapter id="intro">
<title>Introduction</title>
@@ -108,9 +108,9 @@
<pre caption="Upgrading GCC">
# <i>emerge -uav gcc</i>
-<comment>(Please substitute "i686-pc-linux-gnu-3.4.4" with the GCC
+<comment>(Please substitute "i686-pc-linux-gnu-3.4.5" with the GCC
version and CHOST settings you've upgraded to:)</comment>
-# <i>gcc-config i686-pc-linux-gnu-3.4.4</i>
+# <i>gcc-config i686-pc-linux-gnu-3.4.5</i>
# <i>source /etc/profile</i>
<comment>(Rebuilding libtool)</comment>
@@ -192,7 +192,9 @@
<pre caption="Installing gentoolkit and upgrading GCC">
# <i>emerge -an gentoolkit</i>
# <i>emerge -uav gcc</i>
-# <i>gcc-config i686-pc-linux-gnu-3.4.4</i>
+<comment>(Please substitute "i686-pc-linux-gnu-3.4.5" with the GCC
+version and CHOST settings you've upgraded to:)</comment>
+# <i>gcc-config i686-pc-linux-gnu-3.4.5</i>
# <i>source /etc/profile</i>
<comment>(Rebuilding libtool)</comment>
@@ -248,7 +250,9 @@
<pre caption="Upgrading GCC">
# <i>emerge -uav gcc</i>
-# <i>gcc-config i686-pc-linux-gnu-3.4.4</i>
+<comment>(Please substitute "i686-pc-linux-gnu-3.4.5" with the GCC
+version and CHOST settings you've upgraded to:)</comment>
+# <i>gcc-config i686-pc-linux-gnu-3.4.5</i>
# <i>source /etc/profile</i>
<comment>(Rebuilding libtool)</comment>
@@ -333,7 +337,9 @@
<pre caption="Upgrading GCC">
# <i>emerge -uav gcc</i>
-# <i>gcc-config i686-pc-linux-gnu-3.4.4</i>
+<comment>(Please substitute "i686-pc-linux-gnu-3.4.5" with the GCC
+version and CHOST settings you've upgraded to:)</comment>
+# <i>gcc-config i686-pc-linux-gnu-3.4.5</i>
# <i>source /etc/profile</i>
<comment>(Rebuilding libtool)</comment>
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 27+ messages in thread
* [gentoo-doc-cvs] cvs commit: gcc-upgrading.xml
@ 2006-03-01 20:17 Jan Kundrat
0 siblings, 0 replies; 27+ messages in thread
From: Jan Kundrat @ 2006-03-01 20:17 UTC (permalink / raw
To: gentoo-doc-cvs
jkt 06/03/01 20:17:49
Modified: xml/htdocs/doc/en gcc-upgrading.xml
Log:
Removed redundant notes about the need to substitute GCC version and CHOST settings
Revision Changes Path
1.12 +3 -18 xml/htdocs/doc/en/gcc-upgrading.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gcc-upgrading.xml?rev=1.12&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gcc-upgrading.xml?rev=1.12&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gcc-upgrading.xml.diff?r1=1.11&r2=1.12&cvsroot=gentoo
Index: gcc-upgrading.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- gcc-upgrading.xml 1 Mar 2006 01:54:04 -0000 1.11
+++ gcc-upgrading.xml 1 Mar 2006 20:17:49 -0000 1.12
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.11 2006/03/01 01:54:04 vanquirius Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.12 2006/03/01 20:17:49 jkt Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -25,8 +25,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>10</version>
-<date>2006-02-28</date>
+<version>11</version>
+<date>2006-03-01</date>
<chapter id="intro">
<title>Introduction</title>
@@ -201,11 +201,6 @@
# <i>emerge --oneshot -av libtool</i>
</pre>
-<note>
-This assumes that you have <c>CHOST="i686-pc-linux-gnu"</c> set. If you are
-using another CHOST, please use the appropriate gcc-config line.
-</note>
-
<p>
Now, we want to see which packages that revdep-rebuild will want to rebuild.
Then we will tell revdep-rebuild to actually rebuild the packages. This may take
@@ -259,11 +254,6 @@
# <i>emerge --oneshot -av libtool</i>
</pre>
-<note>
-This assumes that you have <c>CHOST="i686-pc-linux-gnu"</c> set. If you are
-using another CHOST, please use the appropriate gcc-config line.
-</note>
-
<p>
To provide compatibility with older binary C++ applications,
<c>sys-libs/libstdc++-v3</c> needs to be merged onto your system.
@@ -346,11 +336,6 @@
# <i>emerge --oneshot -av libtool</i>
</pre>
-<note>
-This assumes that you have <c>CHOST="i686-pc-linux-gnu"</c> set. If you are
-using another CHOST, please use the appropriate gcc-config line.
-</note>
-
<p>
To provide compatibility with older binary C++ applications,
<c>sys-libs/libstdc++-v3</c> needs to be merged onto your system.
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 27+ messages in thread
* [gentoo-doc-cvs] cvs commit: gcc-upgrading.xml
@ 2006-05-26 20:45 Josh Saddler
0 siblings, 0 replies; 27+ messages in thread
From: Josh Saddler @ 2006-05-26 20:45 UTC (permalink / raw
To: gentoo-doc-cvs
nightmorph 06/05/26 20:45:35
Modified: gcc-upgrading.xml
Log:
Updated gcc upgrading guide as per Halcy0n's request
Revision Changes Path
1.13 xml/htdocs/doc/en/gcc-upgrading.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gcc-upgrading.xml?rev=1.13&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gcc-upgrading.xml?rev=1.13&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gcc-upgrading.xml.diff?r1=1.12&r2=1.13&cvsroot=gentoo
Index: gcc-upgrading.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- gcc-upgrading.xml 1 Mar 2006 20:17:49 -0000 1.12
+++ gcc-upgrading.xml 26 May 2006 20:45:35 -0000 1.13
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.12 2006/03/01 20:17:49 jkt Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.13 2006/05/26 20:45:35 nightmorph Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -25,8 +25,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>11</version>
-<date>2006-03-01</date>
+<version>12</version>
+<date>2006-05-26</date>
<chapter id="intro">
<title>Introduction</title>
@@ -60,12 +60,11 @@
using a stage3 tarball, after a new GCC major/minor version has been released.
</p>
-<note>
-It should be noted that upgrading from GCC-3.4 to GCC-4.0 or greater requires
-no real changes to be made by the user, as GCC-3.4 and GCC-4.0 use the same
-ABI. All that is required is that <c>gcc-config</c> is used to select the
-compiler desired.
-</note>
+<warn>
+It should be noted that upgrading from GCC-3.4 to GCC-4.1 or greater still
+requires you to follow the general upgrading instructions, as GCC-3.4 and
+GCC-4.1 use slightly different ABIs.
+</warn>
</body>
</section>
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 27+ messages in thread
* [gentoo-doc-cvs] cvs commit: gcc-upgrading.xml
@ 2006-08-31 0:08 Josh Saddler
0 siblings, 0 replies; 27+ messages in thread
From: Josh Saddler @ 2006-08-31 0:08 UTC (permalink / raw
To: gentoo-doc-cvs
nightmorph 06/08/31 00:08:58
Modified: gcc-upgrading.xml
Log:
Updated gcc guide for bug 145014, thanks to amne for the updates
Revision Changes Path
1.14 xml/htdocs/doc/en/gcc-upgrading.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml?rev=1.14&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml?rev=1.14&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml?r1=1.13&r2=1.14
Index: gcc-upgrading.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- gcc-upgrading.xml 26 May 2006 20:45:35 -0000 1.13
+++ gcc-upgrading.xml 31 Aug 2006 00:08:57 -0000 1.14
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.13 2006/05/26 20:45:35 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.14 2006/08/31 00:08:57 nightmorph Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -25,8 +25,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>12</version>
-<date>2006-05-26</date>
+<version>13</version>
+<date>2006-08-30</date>
<chapter id="intro">
<title>Introduction</title>
@@ -107,18 +107,22 @@
<pre caption="Upgrading GCC">
# <i>emerge -uav gcc</i>
-<comment>(Please substitute "i686-pc-linux-gnu-3.4.5" with the GCC
+<comment>(Please substitute "i686-pc-linux-gnu-4.1.1" with the GCC
version and CHOST settings you've upgraded to:)</comment>
-# <i>gcc-config i686-pc-linux-gnu-3.4.5</i>
+# <i>gcc-config i686-pc-linux-gnu-4.1.1</i>
# <i>source /etc/profile</i>
+<comment>If you upgraded from gcc 3 to 4 (e.g. from 3.4.6 to 4.1.1 in this
+example) you will have to run fix_libtool_files.sh manually</comment>
+# <i>fix_libtool_files.sh 3.4.6</i>
+
<comment>(Rebuilding libtool)</comment>
# <i>emerge --oneshot -av libtool</i>
</pre>
<p>
-Now let's rebuild toolchain and then world so we will make use of the new
-compiler.
+To be completely safe that your system is in a sane state, you <e>must</e>
+rebuild the toolchain and then world to make use of the new compiler.
</p>
<pre caption="Rebuilding system">
@@ -129,11 +133,11 @@
<p>
It is safe to remove the older GCC version at this time. If you feel the need,
please issue the following command (as usual, substitute
-<c>=sys-devel/gcc-3.3*</c> with the version you want to uninstall):
+<c>=sys-devel/gcc-3.4*</c> with the version you want to uninstall):
</p>
<pre caption="Removing older GCC version">
-# <i>emerge -aC =sys-devel/gcc-3.3*</i>
+# <i>emerge -aC =sys-devel/gcc-3.4*</i>
</pre>
</body>
@@ -159,6 +163,11 @@
<body>
<impo>
+If you upgrade from gcc 3.4 to 4.1, please consult the General Update
+instructions.
+</impo>
+
+<impo>
If you're upgrading on a SPARC machine, you will have to take the way of
<uri link="#upgrade-3.3-to-3.4-emerge-e">complete system rebuild</uri> due to
some internal <uri link="http://gcc.gnu.org/gcc-3.4/sparc-abi.html">ABI
@@ -166,13 +175,16 @@
</impo>
<p>
-You have two possibilities on how to upgrade your system. The <uri
-link="#upgrade-3.3-to-3.4-revdep-rebuild">first method</uri> is faster and
-requires use of the <c>revdep-rebuild</c> tool from package <c>gentoolkit</c>
-while the <uri link="#upgrade-3.3-to-3.4-emerge-e">second one</uri> rebuilds the
-entire system from scratch so it will make use of new GCC features. It's up to
-you to decide which of these two ways you will choose. In most cases, the first
-method is sufficient.
+If you upgrade from gcc 3.3 to 3.4, you have two possibilities on how to
+upgrade your system. The <uri link="#upgrade-3.3-to-3.4-revdep-rebuild">first
+method</uri> is faster and requires use of the <c>revdep-rebuild</c> tool from
+package <c>gentoolkit</c> while the <uri
+link="#upgrade-3.3-to-3.4-emerge-e">second one</uri> rebuilds the entire
+system from scratch so it will make use of new GCC features. It's up to you to decide which of these two ways you will choose. In most cases, the first
+method is sufficient.</p>
+<p>If you upgrade from gcc 3.3 to 4.1, do not use the method based on
+revdep-rebuild, but do a <uri link="#upgrade-3.3-to-3.4-emerge-e">complete
+system rebuild</uri>.
</p>
</body>
@@ -249,6 +261,10 @@
# <i>gcc-config i686-pc-linux-gnu-3.4.5</i>
# <i>source /etc/profile</i>
+<comment>If you upgraded from gcc 3 to 4 (e.g. from 3.3.6 to 4.1.1 in this
+example) you will have to run fix_libtool_files.sh manually</comment>
+# <i>fix_libtool_files.sh 3.3.6</i>
+
<comment>(Rebuilding libtool)</comment>
# <i>emerge --oneshot -av libtool</i>
</pre>
@@ -428,8 +444,8 @@
<p>
Always use same GCC version for your kernel and additional kernel modules. Once
you rebuild your world with new GCC, external modules (like
-<c>app-emulation/qemu-softmmu</c>) will fail to load. Please rebuild your kernel
-with new GCC to fix that.
+<c>app-emulation/qemu-softmmu</c>) will fail to load. Please rebuild your
+kernel with the new GCC to fix that.
</p>
<p>
@@ -451,11 +467,11 @@
</p>
<p>
-If you see the <e>error: /usr/bin/gcc-config: line 632:
+If you see <e>error: /usr/bin/gcc-config: line 632:
/etc/env.d/gcc/i686-pc-linux-gnu-3.3.5: No such file or directory</e>, then try
deleting <path>/etc/env.d/gcc/config-i686-pc-linux-gnu</path> and running
-<c>gcc-config</c> again, followed by <c>source /etc/profile</c>. Only do this if
-you do not have any cross-compilers set up, though.
+<c>gcc-config</c> again, followed by <c>source /etc/profile</c>. Only do this
+if you do not have any cross-compilers set up, though.
</p>
<p>
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 27+ messages in thread
* [gentoo-doc-cvs] cvs commit: gcc-upgrading.xml
@ 2006-09-02 4:16 vapier
0 siblings, 0 replies; 27+ messages in thread
From: vapier @ 2006-09-02 4:16 UTC (permalink / raw
To: gentoo-doc-cvs
vapier 06/09/02 04:16:58
Modified: gcc-upgrading.xml
Log:
add a note about minor updates
Revision Changes Path
1.15 xml/htdocs/doc/en/gcc-upgrading.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml?rev=1.15&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml?rev=1.15&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml?r1=1.14&r2=1.15
Index: gcc-upgrading.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- gcc-upgrading.xml 31 Aug 2006 00:08:57 -0000 1.14
+++ gcc-upgrading.xml 2 Sep 2006 04:16:58 -0000 1.15
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.14 2006/08/31 00:08:57 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.15 2006/09/02 04:16:58 vapier Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -44,11 +44,13 @@
</p>
<p>
-If you install a newer version of GCC, the system will not switch over to use it
-automatically. You'll have to explicitly request the change because the
-migration process might require some additional steps. If you decide not to
-switch, Portage will continue to use older version of your compiler until you
-change your mind, or remove the old compiler from the system.
+If you install a new major version of GCC (such as 3.3.6 to 3.4.5), the system
+will not switch over to use it automatically. You'll have to explicitly request
+the change because the migration process might require some additional steps.
+If you decide not to switch, Portage will continue to use older version of your
+compiler until you change your mind, or remove the old compiler from the system.
+Non-major gcc upgrades are switched automatically for you (such as 3.4.5 to
+3.4.6).
</p>
<p>
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 27+ messages in thread
* [gentoo-doc-cvs] cvs commit: gcc-upgrading.xml
@ 2006-09-02 5:18 Lukasz Damentko
0 siblings, 0 replies; 27+ messages in thread
From: Lukasz Damentko @ 2006-09-02 5:18 UTC (permalink / raw
To: gentoo-doc-cvs
rane 06/09/02 05:18:33
Modified: gcc-upgrading.xml
Log:
bumping date and version
Revision Changes Path
1.16 xml/htdocs/doc/en/gcc-upgrading.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml?rev=1.16&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml?rev=1.16&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml?r1=1.15&r2=1.16
Index: gcc-upgrading.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- gcc-upgrading.xml 2 Sep 2006 04:16:58 -0000 1.15
+++ gcc-upgrading.xml 2 Sep 2006 05:18:33 -0000 1.16
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.15 2006/09/02 04:16:58 vapier Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.16 2006/09/02 05:18:33 rane Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -25,8 +25,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>13</version>
-<date>2006-08-30</date>
+<version>14</version>
+<date>2006-09-01</date>
<chapter id="intro">
<title>Introduction</title>
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 27+ messages in thread
* [gentoo-doc-cvs] cvs commit: gcc-upgrading.xml
@ 2006-09-04 20:48 Josh Saddler
0 siblings, 0 replies; 27+ messages in thread
From: Josh Saddler @ 2006-09-04 20:48 UTC (permalink / raw
To: gentoo-doc-cvs
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1740 bytes --]
nightmorph 06/09/04 20:48:18
Modified: gcc-upgrading.xml
Log:
halcy0n is retired; updated email address
Revision Changes Path
1.17 xml/htdocs/doc/en/gcc-upgrading.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml?rev=1.17&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml?rev=1.17&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml?r1=1.16&r2=1.17
Index: gcc-upgrading.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- gcc-upgrading.xml 2 Sep 2006 05:18:33 -0000 1.16
+++ gcc-upgrading.xml 4 Sep 2006 20:48:18 -0000 1.17
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.16 2006/09/02 05:18:33 rane Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.17 2006/09/04 20:48:18 nightmorph Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -13,7 +13,7 @@
<mail link="jkt@gentoo.org">Jan Kundrát</mail>
</author>
<author title="Editor">
- <mail link="halcy0n@gentoo.org">Mark Loeser</mail>
+ <mail link="mark@halc0n.com">Mark Loeser</mail>
</author>
<abstract>
@@ -25,8 +25,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>14</version>
-<date>2006-09-01</date>
+<version>15</version>
+<date>2006-09-04</date>
<chapter id="intro">
<title>Introduction</title>
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 27+ messages in thread
* [gentoo-doc-cvs] cvs commit: gcc-upgrading.xml
@ 2006-09-06 2:14 vapier
0 siblings, 0 replies; 27+ messages in thread
From: vapier @ 2006-09-06 2:14 UTC (permalink / raw
To: gentoo-doc-cvs
vapier 06/09/06 02:14:24
Modified: gcc-upgrading.xml
Log:
Gentoo Linux -> Gentoo
Revision Changes Path
1.19 xml/htdocs/doc/en/gcc-upgrading.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml?rev=1.19&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml?rev=1.19&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml?r1=1.18&r2=1.19
Index: gcc-upgrading.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -r1.18 -r1.19
--- gcc-upgrading.xml 5 Sep 2006 23:26:59 -0000 1.18
+++ gcc-upgrading.xml 6 Sep 2006 02:14:24 -0000 1.19
@@ -1,10 +1,10 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.18 2006/09/05 23:26:59 jkt Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.19 2006/09/06 02:14:24 vapier Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
<guide link="/doc/en/gcc-upgrading.xml">
-<title>Gentoo Linux GCC Upgrade Guide</title>
+<title>Gentoo GCC Upgrade Guide</title>
<author title="Author">
<mail link="amne@gentoo.org">Wernfried Haas</mail>
@@ -18,14 +18,14 @@
<abstract>
This document will guide the user through the process of upgrading GCC on their
-Gentoo Linux machines.
+Gentoo machines.
</abstract>
<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>16</version>
+<version>17</version>
<date>2006-09-06</date>
<chapter id="intro">
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 27+ messages in thread
* [gentoo-doc-cvs] cvs commit: gcc-upgrading.xml
@ 2006-09-07 11:06 Lukasz Damentko
0 siblings, 0 replies; 27+ messages in thread
From: Lukasz Damentko @ 2006-09-07 11:06 UTC (permalink / raw
To: gentoo-doc-cvs
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1680 bytes --]
rane 06/09/07 11:06:40
Modified: gcc-upgrading.xml
Log:
fixing a typo in the halcy0n's mail address
Revision Changes Path
1.20 xml/htdocs/doc/en/gcc-upgrading.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml?rev=1.20&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml?rev=1.20&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml?r1=1.19&r2=1.20
Index: gcc-upgrading.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -r1.19 -r1.20
--- gcc-upgrading.xml 6 Sep 2006 02:14:24 -0000 1.19
+++ gcc-upgrading.xml 7 Sep 2006 11:06:40 -0000 1.20
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.19 2006/09/06 02:14:24 vapier Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.20 2006/09/07 11:06:40 rane Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -13,7 +13,7 @@
<mail link="jkt@gentoo.org">Jan Kundrát</mail>
</author>
<author title="Editor">
- <mail link="mark@halc0n.com">Mark Loeser</mail>
+ <mail link="mark@halcy0n.com">Mark Loeser</mail>
</author>
<abstract>
@@ -25,7 +25,7 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>17</version>
+<version>18</version>
<date>2006-09-06</date>
<chapter id="intro">
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 27+ messages in thread
* [gentoo-doc-cvs] cvs commit: gcc-upgrading.xml
@ 2006-09-13 14:42 Jan Kundrat
0 siblings, 0 replies; 27+ messages in thread
From: Jan Kundrat @ 2006-09-13 14:42 UTC (permalink / raw
To: gentoo-doc-cvs
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>.
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 27+ messages in thread
* [gentoo-doc-cvs] cvs commit: gcc-upgrading.xml
@ 2006-09-13 14:52 Jan Kundrat
0 siblings, 0 replies; 27+ messages in thread
From: Jan Kundrat @ 2006-09-13 14:52 UTC (permalink / raw
To: gentoo-doc-cvs
jkt 06/09/13 14:52:10
Modified: gcc-upgrading.xml
Log:
coding style fixes, *no content change*
Revision Changes Path
1.22 xml/htdocs/doc/en/gcc-upgrading.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml?rev=1.22&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml?rev=1.22&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml?r1=1.21&r2=1.22
Index: gcc-upgrading.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -r1.21 -r1.22
--- gcc-upgrading.xml 13 Sep 2006 14:42:58 -0000 1.21
+++ gcc-upgrading.xml 13 Sep 2006 14:52:10 -0000 1.22
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.21 2006/09/13 14:42:58 jkt Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.22 2006/09/13 14:52:10 jkt Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -187,9 +187,13 @@
method</uri> is faster and requires use of the <c>revdep-rebuild</c> tool from
package <c>gentoolkit</c> while the <uri
link="#upgrade-3.3-to-3.4-emerge-e">second one</uri> rebuilds the entire
-system from scratch so it will make use of new GCC features. It's up to you to decide which of these two ways you will choose. In most cases, the first
-method is sufficient.</p>
-<p>If you upgrade from gcc 3.3 to 4.1, do not use the method based on
+system from scratch so it will make use of new GCC features. It's up to you to
+decide which of these two ways you will choose. In most cases, the first
+method is sufficient.
+</p>
+
+<p>
+If you upgrade from gcc 3.3 to 4.1, do not use the method based on
revdep-rebuild, but do a <uri link="#upgrade-3.3-to-3.4-emerge-e">complete
system rebuild</uri>.
</p>
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 27+ messages in thread
* [gentoo-doc-cvs] cvs commit: gcc-upgrading.xml
@ 2006-09-13 23:20 Jan Kundrat
0 siblings, 0 replies; 27+ messages in thread
From: Jan Kundrat @ 2006-09-13 23:20 UTC (permalink / raw
To: gentoo-doc-cvs
jkt 06/09/13 23:20:10
Modified: gcc-upgrading.xml
Log:
#146857, 3.3 -> 4.1 stuff, part two
Revision Changes Path
1.23 xml/htdocs/doc/en/gcc-upgrading.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml?rev=1.23&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml?rev=1.23&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml?r1=1.22&r2=1.23
Index: gcc-upgrading.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -r1.22 -r1.23
--- gcc-upgrading.xml 13 Sep 2006 14:52:10 -0000 1.22
+++ gcc-upgrading.xml 13 Sep 2006 23:20:10 -0000 1.23
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.22 2006/09/13 14:52:10 jkt Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.23 2006/09/13 23:20:10 jkt Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -25,7 +25,7 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>19</version>
+<version>20</version>
<date>2006-09-13</date>
<chapter id="intro">
@@ -63,8 +63,8 @@
</p>
<warn>
-It should be noted that upgrading from GCC-3.4 to GCC-4.1 or greater still
-requires you to follow the <uri link="#upgrade-general">general upgrading
+It should be noted that upgrading from GCC-3.4 (or 3.3) to GCC-4.1 or greater
+still requires you to follow the <uri link="#upgrade-general">general upgrading
instructions</uri>, as GCC-3.4 and GCC-4.1 use slightly different ABIs.
</warn>
@@ -147,6 +147,12 @@
your old GCC version if you want to use an older kernel.
</impo>
+<impo> <!-- FIXME: do we really want to keep it here? -->
+In case you're upgrading from GCC-3.3, you should run <c>emerge --oneshot
+sys-libs/libstdc++-v3</c> to ensure the proper function of older binary C++
+applications.
+</impo>
+
</body>
</section>
</chapter>
@@ -158,7 +164,7 @@
<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 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>
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 27+ messages in thread
* [gentoo-doc-cvs] cvs commit: gcc-upgrading.xml
@ 2006-09-13 23:39 Jan Kundrat
0 siblings, 0 replies; 27+ messages in thread
From: Jan Kundrat @ 2006-09-13 23:39 UTC (permalink / raw
To: gentoo-doc-cvs
jkt 06/09/13 23:39:00
Modified: gcc-upgrading.xml
Log:
better English as suggested by zlin on #-doc, *no content change*
Revision Changes Path
1.24 xml/htdocs/doc/en/gcc-upgrading.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml?rev=1.24&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml?rev=1.24&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml?r1=1.23&r2=1.24
Index: gcc-upgrading.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -r1.23 -r1.24
--- gcc-upgrading.xml 13 Sep 2006 23:20:10 -0000 1.23
+++ gcc-upgrading.xml 13 Sep 2006 23:39:00 -0000 1.24
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.23 2006/09/13 23:20:10 jkt Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.24 2006/09/13 23:39:00 jkt Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -149,7 +149,7 @@
<impo> <!-- FIXME: do we really want to keep it here? -->
In case you're upgrading from GCC-3.3, you should run <c>emerge --oneshot
-sys-libs/libstdc++-v3</c> to ensure the proper function of older binary C++
+sys-libs/libstdc++-v3</c> to provide compatibility with older binary C++
applications.
</impo>
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 27+ messages in thread
* [gentoo-doc-cvs] cvs commit: gcc-upgrading.xml
@ 2006-10-06 17:41 Josh Saddler
0 siblings, 0 replies; 27+ messages in thread
From: Josh Saddler @ 2006-10-06 17:41 UTC (permalink / raw
To: gentoo-doc-cvs
nightmorph 06/10/06 17:41:37
Modified: gcc-upgrading.xml
Log:
updated gcc-upgrading guide for bug 148126
Revision Changes Path
1.25 xml/htdocs/doc/en/gcc-upgrading.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml?rev=1.25&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml?rev=1.25&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml?r1=1.24&r2=1.25
Index: gcc-upgrading.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v
retrieving revision 1.24
retrieving revision 1.25
diff -u -r1.24 -r1.25
--- gcc-upgrading.xml 13 Sep 2006 23:39:00 -0000 1.24
+++ gcc-upgrading.xml 6 Oct 2006 17:41:37 -0000 1.25
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.24 2006/09/13 23:39:00 jkt Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.25 2006/10/06 17:41:37 nightmorph Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -25,8 +25,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>20</version>
-<date>2006-09-13</date>
+<version>21</version>
+<date>2006-10-06</date>
<chapter id="intro">
<title>Introduction</title>
@@ -112,7 +112,7 @@
<comment>(Please substitute "i686-pc-linux-gnu-4.1.1" with the GCC
version and CHOST settings you've upgraded to:)</comment>
# <i>gcc-config i686-pc-linux-gnu-4.1.1</i>
-# <i>source /etc/profile</i>
+# <i>env-update && source /etc/profile</i>
<comment>If you upgraded from gcc 3 to 4 (e.g. from 3.4.6 to 4.1.1 in this
example) you will have to run fix_libtool_files.sh manually</comment>
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 27+ messages in thread
* [gentoo-doc-cvs] cvs commit: gcc-upgrading.xml
@ 2007-04-02 23:13 Jan Kundrat
0 siblings, 0 replies; 27+ messages in thread
From: Jan Kundrat @ 2007-04-02 23:13 UTC (permalink / raw
To: gentoo-doc-cvs
jkt 07/04/02 23:13:45
Modified: gcc-upgrading.xml
Log:
Kernels 2.4.34+ can be compiled by gcc-4.1. Reported by Gilles Espinasse <g.esp@free.fr>, forwarded by halcy0n.
Revision Changes Path
1.26 xml/htdocs/doc/en/gcc-upgrading.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml?rev=1.26&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml?rev=1.26&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml?r1=1.25&r2=1.26
Index: gcc-upgrading.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v
retrieving revision 1.25
retrieving revision 1.26
diff -u -r1.25 -r1.26
--- gcc-upgrading.xml 6 Oct 2006 17:41:37 -0000 1.25
+++ gcc-upgrading.xml 2 Apr 2007 23:13:45 -0000 1.26
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.25 2006/10/06 17:41:37 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.26 2007/04/02 23:13:45 jkt Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -25,8 +25,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>21</version>
-<date>2006-10-06</date>
+<version>22</version>
+<date>2007-04-03</date>
<chapter id="intro">
<title>Introduction</title>
@@ -143,8 +143,8 @@
</pre>
<impo>
-Please note that the GCC 4.1 and newer can't compile a 2.4 kernel. Don't remove
-your old GCC version if you want to use an older kernel.
+Please note that the GCC 4.1 and newer can compile only kernels newer than
+2.4.34. Don't remove your old GCC version if you want to use an older kernel.
</impo>
<impo> <!-- FIXME: do we really want to keep it here? -->
--
gentoo-doc-cvs@gentoo.org mailing list
^ permalink raw reply [flat|nested] 27+ messages in thread
* [gentoo-doc-cvs] cvs commit: gcc-upgrading.xml
@ 2008-05-19 21:02 Sven Vermeulen
0 siblings, 0 replies; 27+ messages in thread
From: Sven Vermeulen @ 2008-05-19 21:02 UTC (permalink / raw
To: gentoo-doc-cvs
swift 08/05/19 21:02:24
Modified: gcc-upgrading.xml
Log:
Coding style
Revision Changes Path
1.27 xml/htdocs/doc/en/gcc-upgrading.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml?rev=1.27&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml?rev=1.27&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml?r1=1.26&r2=1.27
Index: gcc-upgrading.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v
retrieving revision 1.26
retrieving revision 1.27
diff -u -r1.26 -r1.27
--- gcc-upgrading.xml 2 Apr 2007 23:13:45 -0000 1.26
+++ gcc-upgrading.xml 19 May 2008 21:02:24 -0000 1.27
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.26 2007/04/02 23:13:45 jkt Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.27 2008/05/19 21:02:24 swift Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -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</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>
@@ -124,7 +124,7 @@
<p>
To be completely safe that your system is in a sane state, you <e>must</e>
-rebuild the toolchain and then world to make use of the new compiler.
+rebuild the toolchain and then world to make use of the new compiler.
</p>
<pre caption="Rebuilding system">
--
gentoo-doc-cvs@lists.gentoo.org mailing list
^ permalink raw reply [flat|nested] 27+ messages in thread
* [gentoo-doc-cvs] cvs commit: gcc-upgrading.xml
@ 2008-08-03 3:35 Joshua Saddler
0 siblings, 0 replies; 27+ messages in thread
From: Joshua Saddler @ 2008-08-03 3:35 UTC (permalink / raw
To: gentoo-doc-cvs
nightmorph 08/08/03 03:35:11
Modified: gcc-upgrading.xml
Log:
grammar fix; no content change
Revision Changes Path
1.29 xml/htdocs/doc/en/gcc-upgrading.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml?rev=1.29&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml?rev=1.29&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml?r1=1.28&r2=1.29
Index: gcc-upgrading.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v
retrieving revision 1.28
retrieving revision 1.29
diff -u -r1.28 -r1.29
--- gcc-upgrading.xml 20 Jul 2008 00:34:37 -0000 1.28
+++ gcc-upgrading.xml 3 Aug 2008 03:35:11 -0000 1.29
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.28 2008/07/20 00:34:37 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.29 2008/08/03 03:35:11 nightmorph Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
@@ -20,8 +20,7 @@
</author>
<abstract>
-This document will guide the user through the process of upgrading GCC on their
-Gentoo machines.
+This document will guide the user through the process of upgrading GCC.
</abstract>
<!-- The content of this document is licensed under the CC-BY-SA license -->
^ permalink raw reply [flat|nested] 27+ messages in thread
end of thread, other threads:[~2008-08-03 3:35 UTC | newest]
Thread overview: 27+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-09-07 11:06 [gentoo-doc-cvs] cvs commit: gcc-upgrading.xml Lukasz Damentko
-- strict thread matches above, loose matches on Subject: below --
2008-08-03 3:35 Joshua Saddler
2008-05-19 21:02 Sven Vermeulen
2007-04-02 23:13 Jan Kundrat
2006-10-06 17:41 Josh Saddler
2006-09-13 23:39 Jan Kundrat
2006-09-13 23:20 Jan Kundrat
2006-09-13 14:52 Jan Kundrat
2006-09-13 14:42 Jan Kundrat
2006-09-06 2:14 vapier
2006-09-04 20:48 Josh Saddler
2006-09-02 5:18 Lukasz Damentko
2006-09-02 4:16 vapier
2006-08-31 0:08 Josh Saddler
2006-05-26 20:45 Josh Saddler
2006-03-01 20:17 Jan Kundrat
2006-03-01 1:54 Marcelo Goes
2006-02-25 9:37 Jan Kundrat
2006-02-09 17:40 Jan Kundrat
2006-02-09 16:15 Jan Kundrat
2006-02-09 16:06 Jan Kundrat
2006-02-02 15:59 Xavier Neys
2006-01-30 15:32 Jan Kundrat
2005-12-14 20:03 Jan Kundrat
2005-12-12 15:41 Jan Kundrat
2005-12-08 19:25 Jan Kundrat
2005-12-08 19:21 Jan Kundrat
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox