cc/gcc: always build core pass-1
Up until now, all conditions requiring a core pass-1 was when the
threading implementation used was NPTL. So we only built the core
pass-1 when NPTL was used.
Now, things have changed (what? when? Dunno...), and some bare-metal
canadian toolchains fail to build if a core pass-1 is not present.
OTOH, a core pass-1, although not needed for non-NPTL builds, does
no harm at all if it is present.
So, unconditionally build a core pass-1 (but still pass conditional
options to the core backend).
Reported-by: Per Arnold Blaasmo <Per-Arnold.Blaasmo@atmel.com>
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
1 # Wrapper to build the test suite facilities
3 # Current assumption: test suites are independent of each other
4 # - no order handling required.
6 # List all test suite facilities, and parse their scripts
7 CT_TEST_SUITE_FACILITY_LIST=
8 for f in "${CT_LIB_DIR}/scripts/build/test_suite/"*.sh; do
9 _f="$(basename "${f}" .sh)"
10 __f="CT_TEST_SUITE_${_f}"
11 __f=`echo ${__f} | tr "[:lower:]" "[:upper:]"`
12 if [ "${!__f}" = "y" ]; then
13 CT_DoLog DEBUG "Enabling test suite '${_f}'"
15 CT_TEST_SUITE_FACILITY_LIST="${CT_TEST_SUITE_FACILITY_LIST} ${_f}"
17 CT_DoLog DEBUG "Disabling test suite '${_f}'"
21 # Download the test suite facilities
23 for f in ${CT_TEST_SUITE_FACILITY_LIST}; do
24 do_test_suite_${f}_get
28 # Extract and patch the test suite facilities
29 do_test_suite_extract() {
30 for f in ${CT_TEST_SUITE_FACILITY_LIST}; do
31 do_test_suite_${f}_extract
35 # Build the test suite facilities
37 for f in ${CT_TEST_SUITE_FACILITY_LIST}; do
38 do_test_suite_${f}_build