This is Gentoo's testing wiki. It is a non-operational environment and its textual content is outdated.
Please visit our production wiki at https://wiki.gentoo.org
升级GCC
本文档将指导用户完成GCC的升级。
Please note that downgrading GCC might have unwanted side effects. Refer to the troubleshooting section for some commonly reported issues.
简明版
下一节将给出GCC升级的快速指南（这件事太容易了）。如果你想要阅读升级GCC背后冗长的材料，请继续阅读GCC升级详解。
如果你正在升级GCC，那么你需要做的事情只有改变编译器版本和重新构建libtool。
root #emerge --ask --oneshot sys-devel/gccroot #emerge -u sys-devel/gcc
root #gcc-config -l[1] i686-pc-linux-gnu-4.4.5 * [2] i686-pc-linux-gnu-4.5.3
root #gcc-config 2
root #env-update && source /etc/profileroot #emerge --ask --oneshot --usepkg=n sys-devel/libtoolIf you are upgrading from gcc 4.x to gcc 5.x or later, additional instructions apply; please see then the separate page Upgrading from gcc-4.x to gcc-5.x.
检查当前版本并卸载旧版本：
root #gcc --versionroot #emerge --ask --depclean =sys-devel/gcc-4.4.5After that, verify system integrity running revdep-rebuild:
root #revdep-rebuildEnjoy the new compiler!
GCC 升级详解
GCC升级向来一直都被神秘化了，从“建议你不需要再做任何事情”到“你需要重新编译你的整个系统”。这些恐惧、疑惑、怀疑大多数都源自用户对ABI不兼容性的不够了解。首先先关注下 libtool。
libtool 和 fix_libtool_files.sh
在升级 gcc 版本之后我们需要重新编译 libtool 的原因在于它的主要目的：“libtool” 是一个工具集，通过一个通用的接口聚合了特定平台的代码，允许应用程序使用共享库进行构建，无需应对平台相关的共享库。为能正确实现这一功能，libtool 脚本使用的各种库的定位都包含了 gcc 版本硬编码信息。
ABI 变化
ABI应用程序二进制接口是一个所有处理二进制的程序（包括编译器、汇编器、链接器和语言运行库支持）都会使用的接口（来源：GCC 二进制兼容性）。当二进制程序和库使用的 ABI 改变了之后，你将面临 链接错误或者程序错误的风险，除非你重新编译了所有的使用 C++ 代码的库。
Yes, C++, since most incompatibilities occur within the C++ ABI. If you are upgrading to GCC 4.1, or GCC 5.1, you would probably encounter ABI issues. To prevent this, the revdep-rebuild command should be run against the libstdc++.so.5 library when moving from GCC 3 to GCC 4.1, or libstdc++.so.6 when moving from GCC 4 to GCC 5.1.
root #revdep-rebuild --library 'libstdc\+\+.so.6' -- --exclude gcc那么为什么只有升级到GCC 3.4.0/4.1/5.1版本才需要这么做？这是因为在这之前的版本，GCC采用向下兼容的ABI，这使得你不需要重新编译软件和系统库。当然，我们不能永远保证这种兼容性。如果发生不兼容的情况，libstdc++.so 库将很可能也会升级到更高的版本。
The special case C++11 (and C++14)
While GCC (or more specifically, libstdc++) goes to great lengths to guarantee stability of the ABI, this guarantee does not extend to all parts of C++ within libstdc++. Formally, with versions starting from 3.4, GCC/libstdc++ only guarantees C++98/C++03 ABI stability and not more. This is crucial for packages that depend on C++11. GCC only makes C++11 ABI stability guarantees beginning with version 5.1. This means that switching (even minor) versions of gcc (say from 4.7.3 -> 4.7.4) might cause ABI breakage for binaries built from C++11 code.
For more information and some examples, see:
- bug #513386
- https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61758
- https://blogs.gentoo.org/blueness/2015/03/10/the-c11-abi-incompatibility-problem-in-gentoo/
- https://stackoverflow.com/questions/16190269/g-always-backward-compatible-with-older-static-libraries/16196475#16196475
那些包是已知的要重新构建的?
下面表格给出的包都是需要重新安装的,如果的系统安装过这些包的话,那么请重新构建它们.
| Package | Rebuild needed because ... |
|---|---|
| sys-devel/libtool | libtool application has hardcoded paths towards GCC internal libraries. |
| sys-devel/llvm | depends on exact gcc version, may encounter linking errors with other ebuilds making use of LLVM (e.g. media-libs/mesa) if not rebuilt. |
| sys-devel/clang | depending on exact gcc version, may be affected by sys-devel/llvm. |
root #emerge --ask --oneshot --usepkg=n --verbose sys-devel/libtool sys-devel/llvm sys-devel/clangSome collections of packages need to be built with the same compiler (for example, the various qt-* packages). Such packages are usually bumped by package maintainers simultaneously, so they will always be built with the same GCC version. Cherry-picking re-installs on these packages might prove to be troublesome.
一些人认为当新版本的GCC安装好之后,他们需要重新编译他们系统上的已经安装过的应用,当然,这被认为是没有意义的,因为这里有很多应用在编译和构建的时候并没有用到GCC,所以更新不会影响到它们.
然而并不能说安装好新的GCC并更新应用这种做法是错误的,因为新的GCC版本往往会对进程提供更好的指令集支持,这些支持可能会在某些方面提高一些程序的性能,当然这些影响可能都是轻微的,甚至在某些方面(尤其是特别消耗CPU的应用)并不会提高性能.
Apart from such "benign" benefits, rebuilding everything from scratch may be necessary in some cases to fix problems that don't seem to have any obvious cause.
Some software problems are inherently difficult to diagnose and yet could be solved by simply rebuilding one or more appropriate packages. If such a problem has arisen following a GCC upgrade and persists after using the revdep-rebuild approach described above (and after rebuilding any other obviously relevant packages), a complete system rebuild may be the answer.
The "safest" (but also most time-consuming) way to accomplish this is to use the --emptytree (-e) option of emerge to rebuild the system set and then the world set:
root #emerge --ask --emptytree --usepkg=n @systemroot #emerge --ask --emptytree --usepkg=n @worldUsers are urged to try this approach before reporting any bugs that might have been caused by a GCC upgrade.
(Note that the commands above will cause the packages in the "system" set to be rebuilt twice, which is necessary to be absolutely certain that every package gets built in the same [presumably] "problem-free" environment. Any problems that remain after doing this are due to either "genuine bugs" that should be reported or poor system configuration.)
故障排除
rebuild of boost
If dev-libs/boost needs to be rebuilt, one will get the following error message:
root #emerge ... checking for the Boost _____ library... no configure: error: cannot find the flags to link with Boost _____
One can rebuild with:
root #emerge --ask --oneshot --usepkg=n --verbose dev-libs/boostlibstdc++.so.6: version `GLIBCXX_3.4.15' not found
在升级过程中,你或许会遇到以下面这些错误:
cmake_bootstrap_28021_test: /usr/lib/gcc/i486-pc-linux-gnu/4.1.2/libstdc++.so.6: version `GLIBCXX_3.4.11' not found
这意味着你正在用一个"较老版本"(新版本指的是那些已经构建好这些依赖库的版本)的GCC来构建这些包.请记住所谓的C++ABI 向前兼容指的是:假设你可以用某个版本的GCC成功构建程序和连接库文件,那么你可以用比这个版本更高版本GCC去构建这些程序,而不是用更低版本GCC来构建这些程序.
To rebuild all the packages depending on libstdc++, see the revdep-rebuild instructions above.
另请参阅
- Upgrade GCC up to 4.1, the previous version of this document
- Upgrading from gcc-4.x to gcc-5.x
- Fedora's 'Changes/GCC6' Wiki Page