cc/gcc: cleanup the _or_later logic

So far, we've had a version always select appropriate _or_later option,
which in turn would select all previous _or_later options.

Because the dependencies on companion libs were cumulative, that was
working OK. But the upcoming 4.6 will no longer depend on libelf, so
we can't keep the cumulative scheme we've been using so far.

Have each release family select the corresponding dependencies, instead
of relying on selecting previous _or_later.

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>

# 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() {

    :

}