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)
3 menu "Operating System"
5 # Config option used throughout the config and code to determine wether
6 # we have a kernel or not (there might be different bare metal stuff)...
15 # Each target OS (aka kernel) that support shared libraries can select
16 # this, so the user can decide whether or not to build a shared library
18 config KERNEL_SUPPORTS_SHARED_LIBS
28 source "config.gen/kernel.in"
30 comment "Common kernel options"
34 prompt "Build shared libraries"
35 depends on KERNEL_SUPPORTS_SHARED_LIBS
38 Say 'y' here, unless you don't want shared libraries.
40 You might not want shared libraries if you're building for a target that
41 don't support it (maybe some nommu targets, for example, or bare metal).
43 source "config.gen/kernel.in.2"