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



-- 
[email protected] mailing list

Reply via email to