Move around the BARE_METAL config entry outside of the bare metal /kernel/ entry: there might be different setups that causes a bare metal compiler.
/trunk/config/kernel/bare-metal.experimental.in | 12 4 8 0 ++++--------
/trunk/config/kernel.in | 6 6 0 0 ++++++
2 files changed, 10 insertions(+), 8 deletions(-)
1.1 --- a/config/kernel.in Sun Sep 28 21:30:16 2008 +0000
1.2 +++ b/config/kernel.in Sun Sep 28 21:31:13 2008 +0000
1.3 @@ -2,6 +2,12 @@
1.4
1.5 menu "Operating System"
1.6
1.7 +# Config option used throughout the config and code to determine wether
1.8 +# we hace a kernel or not (there might be different bare metal stuff...
1.9 +config BARE_METAL
1.10 + bool
1.11 + default n
1.12 +
1.13 config KERNEL
1.14 string
1.15
2.1 --- a/config/kernel/bare-metal.experimental.in Sun Sep 28 21:30:16 2008 +0000
2.2 +++ b/config/kernel/bare-metal.experimental.in Sun Sep 28 21:31:13 2008 +0000
2.3 @@ -3,13 +3,9 @@
2.4 config KERNEL_bare_metal
2.5 select BARE_METAL
2.6 help
2.7 - Say 'y' here if you want a simple C compiler with no C library.
2.8 -
2.9 - 'Bare metal' also refer to those programs that run without any kernel.
2.10 + 'Bare metal' refers to those programs that run without any kernel.
2.11
2.12 You probably want to say 'y' here if you plan to use your compiler
2.13 - to build only kernels or bootloaders.
2.14 -
2.15 -config BARE_METAL
2.16 - bool
2.17 - default n
2.18 + to build bootloaders. It is not yet suitable to build Linux kernels,
2.19 + though, because the APCI stuff relies on the target C library headers
2.20 + being available?!?!...