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 file declares functions for bare metal kernel (IE. none)

# Copyright 2008 Yann E. MORIN

# Licensed under the GPL v2. See COPYING in the root of this package

CT_DoKernelTupleValues() {

    # For bare-metal, there is no kernel part in the tuple

    CT_TARGET_KERNEL=

}

do_kernel_get() {

    :

}

do_kernel_extract() {

    :

}

do_kernel_headers() {

    :

}