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 # Menu for the cross GDB
7 select GDB_GDBSERVER if ! BARE_METAL
9 Build and install a cross-gdb for the target, to run on host.
13 config GDB_CROSS_STATIC
15 prompt "Build a static cross gdb"
18 A static cross gdb can be usefull if you debug on a machine that is
19 not the one that is used to compile the toolchain.
21 That way, you can share the cross-gdb without installing a toolchain
22 on every machine that will be used to debug target programs.
24 config GDB_CROSS_USE_GMP_MPFR
31 gdb can use GMP+MPFR, although it does not seem compulsory.
33 Say 'Y' here if you want to use GMP+MPFR.
35 config GDB_CROSS_USE_MPC
39 select GDB_CROSS_USE_GMP_MPFR
42 gdb can use MPC, although it does not seem compulsory.
44 Say 'Y' here if you want to use MPC.