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>
1 reporter_name="Anthony Foiani <anthony.foiani@gmail.com>"
2 reporter_url="http://sourceware.org/ml/crossgcc/2010-09/msg00100.html"
3 reporter_comment="This is a sample config file for Freescale e500v2 processors (e.g.,
4 MPC8548, MPC8572). It uses eglibc (for e500/SPE patches) and a recent
5 gcc (4.5.1, for e500v2 DPFP support) and will generate appropriate
6 dual-precision floating point instructions by default.
8 Note: If building a Linux kernel with this toolchain, you will want to
9 make sure -mno-spe AND -mspe=no are passed to gcc to prevent SPE
10 ABI/instructions from getting into the kernel (which is currently
11 unsupported). At this time, the kernel build system passes those
12 teo options, but older kernels were only passing -mno-spe by default."