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(-)

2 files changed, 10 insertions, 8 deletions

diff --git a/config/kernel.in b/config/kernel.in
index 1ae8b2e6..a2a96860 100644
--- a/config/kernel.in
+++ b/config/kernel.in
@@ -2,6 +2,12 @@
 
 menu "Operating System"
 
+# Config option used throughout the config and code to determine wether
+# we hace a kernel or not (there might be different bare metal stuff...
+config BARE_METAL
+    bool
+    default n
+
 config KERNEL
     string
 
diff --git a/config/kernel/bare-metal.experimental.in b/config/kernel/bare-metal.experimental.in
index 7a4b5740..a05b97ea 100644
--- a/config/kernel/bare-metal.experimental.in
+++ b/config/kernel/bare-metal.experimental.in
@@ -3,13 +3,9 @@
 config KERNEL_bare_metal
     select BARE_METAL
     help
-      Say 'y' here if you want a simple C compiler with no C library.
-      
-      'Bare metal' also refer to those programs that run without any kernel.
+      'Bare metal' refers to those programs that run without any kernel.
       
       You probably want to say 'y' here if you plan to use your compiler
-      to build only kernels or bootloaders.
-
-config BARE_METAL
-    bool
-    default n
+      to build bootloaders. It is not yet suitable to build Linux kernels,
+      though, because the APCI stuff relies on the target C library headers
+      being available?!?!...