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>
5 do_companion_tools_m4_get() {
6 CT_GetFile "m4-${CT_M4_VERSION}" \
7 {ftp,http}://ftp.gnu.org/gnu/m4
10 do_companion_tools_m4_extract() {
11 CT_Extract "m4-${CT_M4_VERSION}"
12 CT_Patch "m4" "${CT_M4_VERSION}"
15 do_companion_tools_m4_build() {
16 CT_DoStep EXTRA "Installing m4"
17 mkdir -p "${CT_BUILD_DIR}/build-m4"
18 CT_Pushd "${CT_BUILD_DIR}/build-m4"
21 "${CT_SRC_DIR}/m4-${CT_M4_VERSION}/configure" \
22 --prefix="${CT_BUILDTOOLS_PREFIX_DIR}"
24 CT_DoExecLog ALL make install