nightmorph 08/07/20 00:34:37 Modified: change-chost.xml gcc-upgrading.xml Log: updated gcc upgrading and changing chost guides for bug 232193: the location of fix_libtool_files.sh has changed.
Revision Changes Path 1.5 xml/htdocs/doc/en/change-chost.xml file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/change-chost.xml?rev=1.5&view=markup plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/change-chost.xml?rev=1.5&content-type=text/plain diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/change-chost.xml?r1=1.4&r2=1.5 Index: change-chost.xml =================================================================== RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/change-chost.xml,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- change-chost.xml 23 May 2008 19:42:54 -0000 1.4 +++ change-chost.xml 20 Jul 2008 00:34:37 -0000 1.5 @@ -1,6 +1,6 @@ <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> -<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/change-chost.xml,v 1.4 2008/05/23 19:42:54 swift Exp $ --> +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/change-chost.xml,v 1.5 2008/07/20 00:34:37 nightmorph Exp $ --> <guide link="/doc/en/change-chost.xml" lang="en"> @@ -24,8 +24,8 @@ <!-- See http://creativecommons.org/licenses/by-sa/2.5 --> <license/> -<version>2</version> -<date>2007-07-16</date> +<version>3</version> +<date>2008-07-29</date> <chapter> <title>Introduction</title> @@ -254,13 +254,16 @@ <p> Now it is necessary to re-emerge <c>libtool</c> and run -<c>fix_libtool_files.sh</c>. Make sure to use the correct gcc version: (your -current one, 4.1.1 here, and the old architecture, i386 here). +<c>/usr/share/gcc-data/$CHOST/<gcc-version>/fix_libtool_files.sh</c>. Make +sure to use the correct gcc version (your current one, 4.1.1 here, and the old +architecture, i386 here). Replace $CHOST with your new CHOST, and +<gcc-version> with your gcc version. This example assumes a CHOST of +i686. </p> <pre caption="Ensuring library sanity"> # <i>emerge -av1 libtool</i> -# <i>fix_libtool_files.sh 4.1.1 --oldarch i386-pc-linux-gnu</i> +# <i>/usr/share/gcc-data/i686-pc-linux-gnu/4.1.1/fix_libtool_files.sh 4.1.1 --oldarch i386-pc-linux-gnu</i> </pre> <p> 1.28 xml/htdocs/doc/en/gcc-upgrading.xml file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml?rev=1.28&view=markup plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml?rev=1.28&content-type=text/plain diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml?r1=1.27&r2=1.28 Index: gcc-upgrading.xml =================================================================== RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v retrieving revision 1.27 retrieving revision 1.28 diff -u -r1.27 -r1.28 --- gcc-upgrading.xml 19 May 2008 21:02:24 -0000 1.27 +++ gcc-upgrading.xml 20 Jul 2008 00:34:37 -0000 1.28 @@ -1,5 +1,5 @@ <?xml version='1.0' encoding="UTF-8"?> -<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.27 2008/05/19 21:02:24 swift Exp $ --> +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gcc-upgrading.xml,v 1.28 2008/07/20 00:34:37 nightmorph Exp $ --> <!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> @@ -13,7 +13,10 @@ <mail link="[EMAIL PROTECTED]">Jan Kundrát</mail> </author> <author title="Editor"> - <mail link="[EMAIL PROTECTED]">Mark Loeser</mail> + <mail link="halcy0n"/> +</author> +<author title="Editor"> + <mail link="nightmorph"/> </author> <abstract> @@ -25,8 +28,8 @@ <!-- See http://creativecommons.org/licenses/by-sa/2.5 --> <license/> -<version>22</version> -<date>2007-04-03</date> +<version>23</version> +<date>2008-07-19</date> <chapter id="intro"> <title>Introduction</title> @@ -116,7 +119,9 @@ <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>(Replace $CHOST with your actual CHOST, found in /etc/make.conf)</comment> +<comment>(Replace <gcc-version> with your new, updated GCC version)</comment> +# <i>/usr/share/gcc-data/$CHOST/<gcc-version>/fix_libtool_files.sh 3.4.6</i> <comment>(Rebuilding libtool)</comment> # <i>emerge --oneshot -av libtool</i> @@ -280,7 +285,9 @@ <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>(Replace $CHOST with your actual CHOST, found in /etc/make.conf)</comment> +<comment>(Replace <gcc-version> with your new, updated GCC version)</comment> +# <i>/usr/share/gcc-data/$CHOST/<gcc-version>/fix_libtool_files.sh 3.3.6</i> <comment>(Rebuilding libtool)</comment> # <i>emerge --oneshot -av libtool</i> @@ -479,8 +486,10 @@ <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). +archive</e>, please run +<c>/usr/share/gcc-data/$CHOST/<gcc-version>/fix_libtool_files.sh 3.3.6</c> +(substitute "3.3.6" with the version numbers from the error message, and $CHOST +and <gcc-version> with your actual CHOST and GCC version). </p> <p>
