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>

 CT_EXPERIMENTAL=y

 CT_LOCAL_TARBALLS_DIR="${HOME}/src"

 CT_SAVE_TARBALLS=y

 CT_LOG_EXTRA=y

 CT_ARCH_mips=y

 CT_TARGET_VENDOR="malta"

 CT_KERNEL_linux=y

 CT_KERNEL_V_2_6_38_8=y

 CT_BINUTILS_V_2_21_1a=y

 CT_CC_V_4_4_6=y

 # CT_CC_GCC_USE_GRAPHITE is not set

 CT_LIBC_EGLIBC_V_2_13=y

 CT_DEBUG_gdb=y

 # CT_GDB_GDBSERVER_STATIC is not set

 CT_GDB_V_7_2a=y

 CT_GMP_V_5_0_1=y

 CT_MPFR_V_3_0_0=y

 CT_TEST_SUITE_GCC=y