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 # Compute ARM-specific values
3 CT_DoArchTupleValues() {
4 # The architecture part of the tuple:
5 CT_TARGET_ARCH="${CT_ARCH}${target_endian_eb}"
7 # The system part of the tuple:
8 case "${CT_LIBC},${CT_ARCH_ARM_EABI}" in
9 *glibc,y) CT_TARGET_SYS=gnueabi;;
10 uClibc,y) CT_TARGET_SYS=uclibcgnueabi;;
11 *,y) CT_TARGET_SYS=eabi;;
14 # Set the default instruction set mode
15 case "${CT_ARCH_ARM_MODE}" in
18 CT_ARCH_CC_CORE_EXTRA_CONFIG="--with-mode=thumb"
19 CT_ARCH_CC_EXTRA_CONFIG="--with-mode=thumb"
20 # CT_ARCH_TARGET_CFLAGS="-mthumb"
24 if [ "${CT_ARCH_ARM_INTERWORKING}" = "y" ]; then
25 CT_ARCH_TARGET_CFLAGS+=" -mthumb-interwork"