USE flags for sys-devel/binutils Tools necessary to build programs
||Set ld to point to ld.gold instead of ld.bfd|
||Add extra documentation (API, Javadoc, etc). It is recommended to enable per package instead of globally|
||Build ld.gold linker|
||Build and install gtk-doc based developer documentation for dev-util/devhelp, IDE and offline use|
||Adds support to binutils for cross compiling (does not work with gas)|
||Add Native Language Support (using gettext - GNU locale utilities)|
||Enable plugin support in tools|
||!!do not set this during bootstrap!! Causes binaries to be statically linked instead of dynamically|
||Build static versions of dynamic libraries as well|
||Enable dependencies and/or preparations necessary to run tests (usually controlled by FEATURES=test but can be toggled independently)|
emerge --ask sys-devel/binutils
Select a newer version
Upon binutils package upgrades it is occasionally necessary to select a newer profile to be used for the system's toolchain. This can be done using the binutils-config command. First list known (installed) versions:
 x86_64-pc-linux-gnu-2.25.1 *  x86_64-pc-linux-gnu-2.26.1
Select the newest profile. Either the integer number or the full profile name can be used to select the profile; below the profile name is used:
* Switching to x86_64-pc-linux-gnu-2.26.1 ... [ ok ] * Please remember to run: * # . /etc/profile
Alternatively one can use the eselect binutils command instead of binutils-config.
There are several command-line tools for binary manipulation distributed in binutils, each has its own expectation on acceptable options, arguments, and parameters. Covering them all goes beyond the scope of this article, however they may eventually be expounded upon in the future. See upstream documentation or the appropriate man page for usage on each utility.
When Portage is caught in a
@preserved-rebuild loop and the only culprit failing is binutils, use the following steps to resolve the issue. First use the binutils-config command to select the latest emerged version. See Select a new version section above. After executing this step, return here and perform a
emerge --ask --depclean
Finally perform a
@preserved-rebuild a final time:
emerge --ask @preserved-rebuild
Generally speaking this collection of software tools should only have old versions removed by passing the
--depclean option to emerge.
emerge --ask --depclean --verbose sys-devel/binutils
- Upgrading GCC - Gentoo's long-standing guide containing end-user instructions for upgrading GCC.