config/test_suite.in
author "Yann E. MORIN" <yann.morin.1998@free.fr>
Tue Oct 16 20:57:44 2012 +0200 (2012-10-16)
changeset 3079 37831a33e07e
parent 1965 e3d532dd8b5d
child 3150 1d6fd9bde73c
permissions -rw-r--r--
kernel/linux: fix using custom location

Currently, extract and patch are skipped as thus:
- using a custom directory of pre-installed headers
- a correctly named directory already exists

Otherwise, extract and patch are done.

The current second condition is wrong, because it allows the following
sequence to happen:
- a non-custom kernel is used
- a previous build only partially extracted the non-custom sources
- that p[revious build broke during extraction (eg. incomplete tarball...)
- a subsequent build will find a properly named directory, and will
thus skip extract and patch, which is wrong

Fix that by following the conditions in this table:

Type | Extract | Patch
----------------------+---------+-------
Pre-installed headers | N | N
custom directory | N | N
custom tarball | Y | N
mainstream tarball | Y | Y

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: David Holsgrove <david.holsgrove@xilinx.com>
     1 # Test suite config options
     2 
     3 if EXPERIMENTAL
     4 
     5 menu "Test suite"
     6 
     7 config TEST_SUITE
     8     bool
     9 
    10 config TEST_SUITE_GCC
    11     bool
    12     prompt "GCC test suite"
    13     depends on EXPERIMENTAL
    14     select TEST_SUITE
    15     help
    16       Select this option to install the GCC test suite in $CT_PREFIX_DIR/test_suite.
    17 
    18       The GCC test suite includes a collection of various toolchain tests for GCC -
    19       it utilizes the DejaGnu test framework.
    20 
    21       For some tests a network enabled target with ssh server is required.
    22 
    23       A helper Makefile is provided for running the tests - please see the included
    24       README for information on how to run the test suite.
    25 
    26 endmenu
    27 
    28 endif