Attachment 95504 Details for Bug 145014 – Proposed changes again, this time as diff

[patch] Proposed changes again, this time as diff

diff (text/plain), 3.44 KB, created by Wernfried Haas (RETIRED) on 2006-08-30 12:11:14 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Wernfried Haas (RETIRED)

Created: 2006-08-30 12:11:14 UTC

Size: 3.44 KB

patch

obsolete

>--- gcc-upgrading.xml	2006-08-30 21:03:17.000000000 +0200
>+++ gcc-upgrading-changed.xml	2006-08-30 21:02:23.000000000 +0200
>@@ -107,18 +107,22 @@
> <pre caption="Upgrading GCC">
> # emerge -uav gcc
> 
>-<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>
>-# gcc-config i686-pc-linux-gnu-3.4.5
>+# gcc-config i686-pc-linux-gnu-4.1.1
> # source /etc/profile
> 
>+<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>
>+# fix_libtool_files.sh 3.4.6
>+
> <comment>(Rebuilding libtool)</comment>
> # emerge --oneshot -av libtool
> </pre>
> 
> 
>-Now let's rebuild toolchain and then world so we will make use of the new
>-compiler.
>+To be completely safe that the system is in a sane state, it is necessary to 
>+rebuild toolchain and then world to make use of the new compiler. 
> 
> 
> <pre caption="Rebuilding system">
>@@ -129,11 +133,11 @@
> 
> 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):
> 
> 
> <pre caption="Removing older GCC version">
>-# emerge -aC =sys-devel/gcc-3.3*
>+# emerge -aC =sys-devel/gcc-3.4*
> </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>
> 
> 
>-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.
>+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>.
> 
> 
> </body>
>@@ -249,6 +261,10 @@
> # gcc-config i686-pc-linux-gnu-3.4.5
> # source /etc/profile
> 
>+<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>
>+# fix_libtool_files.sh 3.3.6
>+
> <comment>(Rebuilding libtool)</comment>
> # emerge --oneshot -av libtool
> </pre>

Actions: View | Diff

Attachments on bug 145014: 95503 | 95504