Common Pitfalls

-6 +7 2006-02-09 @@ -295,69 +295,6 @@ - -Common Pitfalls -

- - -

-It's important to disable distcc during upgrade. Mixing compiler versions -on your nodes will cause build issues. This is not required for ccache, -as the cache objects will be invalidated anyway. -

- -

-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. -

- - -

-Frequent Error Messages - - -

-If your system complains about something like libtool: link: -`/usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.6/libstdc++.la' is not a valid libtool -archive, please run /sbin/fix_libtool_files.sh 3.3.6 (substitute -"3.3.6" with the version numbers from the error message). -

- -

-If you see the 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. -

- -

-If a package fails during emerge -e system or emerge -e world, -you can resume operation with emerge --resume. If a package fails -repeatedly, skip it with emerge --resume --skipfirst. Don't run any -other instances of emerge in between or you will lose the resume information. -

- -

-If you get an error message spec failure: unrecognized spec option while -upgrading your compiler, try to switch back to your default compiler, unset the -GCC_SPECS variable and upgrade GCC again: -

- -

-# gcc-config 1
-# source /etc/profile
-# unset GCC_SPECS
-# emerge -uav gcc
-

- - -

- - Upgrading to GCC on a First Install

@@ -503,4 +440,67 @@

+ + +Common Pitfalls +

+ + +

+It's important to disable distcc during upgrade. Mixing compiler versions +on your nodes will cause build issues. This is not required for ccache, +as the cache objects will be invalidated anyway. +

+ +

+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. +

+ + +

+Frequent Error Messages + + +

+If your system complains about something like libtool: link: +`/usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.6/libstdc++.la' is not a valid libtool +archive, please run /sbin/fix_libtool_files.sh 3.3.6 (substitute +"3.3.6" with the version numbers from the error message). +

+ +

+If you see the 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. +

+ +

+If a package fails during emerge -e system or emerge -e world, +you can resume operation with emerge --resume. If a package fails +repeatedly, skip it with emerge --resume --skipfirst. Don't run any +other instances of emerge in between or you will lose the resume information. +

+ +

+If you get an error message spec failure: unrecognized spec option while +upgrading your compiler, try to switch back to your default compiler, unset the +GCC_SPECS variable and upgrade GCC again: +

+ +

+# gcc-config 1
+# source /etc/profile
+# unset GCC_SPECS
+# emerge -uav gcc
+

+ + +

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