Introduction

From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1GIa7S-0002Bq-2Y for garchives@archives.gentoo.org; Thu, 31 Aug 2006 00:09:18 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.7/8.13.6) with SMTP id k7V08xVk003741; Thu, 31 Aug 2006 00:08:59 GMT Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by robin.gentoo.org (8.13.7/8.13.6) with ESMTP id k7V08wcE027196 for ; Thu, 31 Aug 2006 00:08:58 GMT Received: from lark (lark.gentoo.osuosl.org [140.211.166.177]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with SMTP id 3CAE76433A for ; Thu, 31 Aug 2006 00:08:58 +0000 (UTC) Received: by lark (sSMTP sendmail emulation); Thu, 31 Aug 2006 00:08:58 +0000 From: "Josh Saddler" Date: Thu, 31 Aug 2006 00:08:58 +0000 To: gentoo-doc-cvs@lists.gentoo.org Subject: [gentoo-doc-cvs] cvs commit: gcc-upgrading.xml Message-Id: <20060831000858.3CAE76433A@smtp.gentoo.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-doc-cvs@gentoo.org Reply-to: docs-team@lists.gentoo.org X-Archives-Salt: 020273df-1f00-40f6-8563-994457662e3d X-Archives-Hash: 0be61d6aa515f477d8c425f6a5146f8a 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 @@ - + @@ -25,8 +25,8 @@ -12 -2006-05-26 +13 +2006-08-30 Introduction @@ -107,18 +107,22 @@

 # emerge -uav gcc
 
-(Please substitute "i686-pc-linux-gnu-3.4.5" with the GCC
+(Please substitute "i686-pc-linux-gnu-4.1.1" with the GCC
 version and CHOST settings you've upgraded to:)
-# gcc-config i686-pc-linux-gnu-3.4.5
+# gcc-config i686-pc-linux-gnu-4.1.1
 # source /etc/profile
 
+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
+# fix_libtool_files.sh 3.4.6
+
 (Rebuilding libtool)
 # emerge --oneshot -av libtool

-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 must +rebuild the toolchain and then world to make use of the new compiler.

@@ -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
-=sys-devel/gcc-3.3* with the version you want to uninstall):
+=sys-devel/gcc-3.4* with the version you want to uninstall):
 
 
 -# emerge -aC =sys-devel/gcc-3.3*
+# emerge -aC =sys-devel/gcc-3.4*
 
 
 
@@ -159,6 +163,11 @@
 
 
 
+If you upgrade from gcc 3.4 to 4.1, please consult the General Update
+instructions.
+
+
+
 If you're upgrading on a SPARC machine, you will have to take the way of
 complete system rebuild due to
 some internal ABI
@@ -166,13 +175,16 @@
 
 
 
-You have two possibilities on how to upgrade your system. The first method is faster and
-requires use of the revdep-rebuild tool from package gentoolkit
-while the second one 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 first
+method is faster and requires use of the revdep-rebuild tool from
+package gentoolkit while the second one 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 complete
+system rebuild.
 
 
 
@@ -249,6 +261,10 @@
 # gcc-config i686-pc-linux-gnu-3.4.5
 # source /etc/profile
 
+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
+# fix_libtool_files.sh 3.3.6
+
 (Rebuilding libtool)
 # emerge --oneshot -av libtool

@@ -428,8 +444,8 @@

Always use same GCC version for your kernel and additional kernel modules. Once you rebuild your world with new GCC, external modules (like -app-emulation/qemu-softmmu) will fail to load. Please rebuild your kernel -with new GCC to fix that. +app-emulation/qemu-softmmu) will fail to load. Please rebuild your +kernel with the new GCC to fix that.

@@ -451,11 +467,11 @@

-If you see the error: /usr/bin/gcc-config: line 632: +If you see error: /usr/bin/gcc-config: line 632: /etc/env.d/gcc/i686-pc-linux-gnu-3.3.5: No such file or directory, then try deleting /etc/env.d/gcc/config-i686-pc-linux-gnu and running -gcc-config again, followed by source /etc/profile. Only do this if -you do not have any cross-compilers set up, though. +gcc-config again, followed by source /etc/profile. Only do this +if you do not have any cross-compilers set up, though.

-- gentoo-doc-cvs@gentoo.org mailing list