config/kernel/bare-metal.in
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Fri Oct 08 23:37:12 2010 +0200 (2010-10-08)
branch1.8
changeset 2150 f97a8ad2b172
parent 890 6227df6bbb79
child 2444 896cb0d36c1a
permissions -rw-r--r--
cc/gcc: fix C++ headers location

In case we build the C++ compiler, we have to tell gcc where to put the C++
headers, or else it will try to # put it in prefix/tuple/include, which we
make a symlink to sysroot/usr/include during the build, and that we delete
(the symlink!) after the build, but gcc will not look in sysroot/usr/inlcude
for C++ headers by default.

Implements a fix suggested by: Bryan Hundven <bryanhundven@gmail.com>

Reported-by: Anthony Foiani <anthony.foiani@gmail.com>
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
(transplanted from a0924619112015bdaa81a0a2313d21ef38607bc2)
     1 # Bare metal config options
     2 
     3 config KERNEL_bare_metal
     4     select BARE_METAL
     5     help
     6       'Bare metal' refers to those programs that run without any kernel.
     7       
     8       You probably want to say 'y' here if you plan to use your compiler
     9       to build bootloaders. It is not yet suitable to build Linux kernels,
    10       though, because the APCI stuff relies on the target C library headers
    11       being available?!?!...