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>

 # dmalloc debug facility

 # depends on ! BACKEND

 config DEBUG_dmalloc

     bool

 choice

     bool

     prompt "dmalloc version"

 # Don't remove next line

 # CT_INSERT_VERSION_BELOW

 config DMALLOC_V_5_5_2

     bool

     prompt "5.5.2"

 endchoice

 config DMALLOC_VERSION

     string

 # Don't remove next line

 # CT_INSERT_VERSION_STRING_BELOW

     default "5.5.2" if DMALLOC_V_5_5_2