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>

 # Bare metal config options

 config KERNEL_bare_metal

     select BARE_METAL

     help

       'Bare metal' refers to those programs that run without any kernel.

       You probably want to say 'y' here if you plan to use your compiler

       to build bootloaders. It is not yet suitable to build Linux kernels,

       though, because the APCI stuff relies on the target C library headers

       being available?!?!...