config/kernel/bare-metal.in
author |
"Yann E. MORIN" <yann.morin.1998@free.fr> |
|
Wed Aug 01 19:02:06 2012 +0200 (2012-08-01) |
changeset 3023 |
c71635732a59 |
parent 1030 |
e5bf882d6514
|
permissions |
-rw-r--r-- |
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>
yann@861
|
1 |
# Bare metal config options
|
yann@861
|
2 |
|
yann@2444
|
3 |
## select BARE_METAL
|
yann@2444
|
4 |
##
|
yann@2444
|
5 |
## help 'Bare metal' refers to those programs that run without any kernel.
|
yann@2444
|
6 |
## help
|
yann@2444
|
7 |
## help You probably want to say 'y' here if you plan to use your compiler
|
yann@2444
|
8 |
## help to build bootloaders. It is not yet suitable to build Linux kernels,
|
yann@2444
|
9 |
## help though, because the APCI stuff relies on the target C library headers
|
yann@2444
|
10 |
## help being available?!?!...
|