config/test_suite.in
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Mon Mar 28 01:05:18 2011 +0200 (2011-03-28)
changeset 2362 0888065f8c4d
child 2484 d1a8c2ae7946
permissions -rw-r--r--
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>
     1 # Test suite config options
     2 
     3 if EXPERIMENTAL
     4 
     5 menu "Test suite"
     6 
     7 config TEST_SUITE
     8     bool
     9     default n
    10 
    11 config TEST_SUITE_GCC
    12     bool
    13     prompt "GCC test suite"
    14     depends on EXPERIMENTAL
    15     default n
    16     select TEST_SUITE
    17     help
    18       Select this option to install the GCC test suite in $CT_PREFIX_DIR/test_suite.
    19 
    20       The GCC test suite includes a collection of various toolchain tests for GCC -
    21       it utilizes the DejaGnu test framework.
    22 
    23       For some tests a network enabled target with ssh server is required.
    24 
    25       A helper Makefile is provided for running the tests - please see the included 
    26       README for information on how to run the test suite.
    27 
    28 endmenu
    29 
    30 endif