binutils/binutils: simplify gold dependencies

In preparation of adding a new kernel-type, Yann D. came up
with a change in semantic on binutils/gold availability.

So far, it was architectures' responsibility to declare that
they did support binutils/gold or not. It makes much more sense
that binutils/gold declares its own availability depending on
the current architecture; after all, architectures have no way
to know wether gold supports them, while gold does know it.

Signed-off-by:Yann Diorcet <diorcet.yann@gmail.com>
[yann.morin.1998@free.fr: split up original patch for self-contained changes]
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Message-Id: <d3d1d51f399e6d2c1163.1353320546@macbook-smorlat.local>
Patchwork-Id: 199971
This commit is contained in:
Yann Diorcet 2012-11-19 21:45:09 +01:00
parent 7b7f7e4db2
commit 19fa6609da

View File

@ -115,8 +115,11 @@ config BINUTILS_HAS_HASH_STYLE
config BINUTILS_HAS_GOLD
bool
# gold only suports the listed architectures
config BINUTILS_GOLD_SUPPORTS_ARCH
bool
default y if ARCH_arm
default y if ARCH_x86
config BINUTILS_HAS_PLUGINS
bool
@ -124,13 +127,6 @@ config BINUTILS_HAS_PLUGINS
config BINUTILS_HAS_PKGVERSION_BUGURL
bool
# Only these architectures have support in gold
config ARCH_arm
select BINUTILS_GOLD_SUPPORTS_ARCH
config ARCH_x86
select BINUTILS_GOLD_SUPPORTS_ARCH
# Force using the BFD linker if needed
# This is the case for some C libraries (eg. glibc and
# eglibc at least) and affected components can select this