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.1 --- a/scripts/build/cc/gcc.sh Wed Aug 01 22:02:26 2012 +0200
1.2 +++ b/scripts/build/cc/gcc.sh Wed Aug 01 19:02:06 2012 +0200
1.3 @@ -88,6 +88,15 @@
1.4 core_opts+=( "cflags=${CT_CFLAGS_FOR_HOST}" )
1.5 core_opts+=( "lang_list=c" )
1.6 ;;
1.7 + *)
1.8 + do_core=y
1.9 + core_opts+=( "mode=static" )
1.10 + core_opts+=( "host=${CT_BUILD}" )
1.11 + core_opts+=( "complibs=${CT_BUILDTOOLS_PREFIX_DIR}" )
1.12 + core_opts+=( "prefix=${CT_BUILDTOOLS_PREFIX_DIR}" )
1.13 + core_opts+=( "cflags=${CT_CFLAGS_FOR_HOST}" )
1.14 + core_opts+=( "lang_list=c" )
1.15 + ;;
1.16 esac
1.17
1.18 if [ "${do_core}" = "y" ]; then