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> -- [email protected] mailing list
