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>

syntax: glob

# Generated files

configure

autom4te.cache

config.log

config.status

Makefile

*ct-ng*

docs/*ct-ng*.1

docs/*ct-ng*.1.gz

paths.mk

paths.sh

scripts/crosstool-NG.sh

scripts/saveSample.sh

scripts/showTuple.sh

kconfig/conf

kconfig/?conf

kconfig/**.o

kconfig/**.dep

kconfig/lex.backup

kconfig/lex.zconf.c

kconfig/zconf.hash.c

kconfig/zconf.tab.c

config/configure.in

config.gen/

.config

.config.2

# Temporaries

.*.swp

build.log

.config.old

# This is the place where toolchains are built

.build/

# .. and the legacy location

targets/