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 This is a somewhat ordered TODO list:
5 - update versions for every tools...
7 - update and/or upgrade all samples
12 - update newlib (for enhanced bare metal)
13 - confirm existing implementation on targets other than AVR32
14 - try to make it generic, will help for uClibc++
18 - Cygwin target (needs newlib)
19 - so we can build toolchains that generate code for Windows/Cygwin
22 - so we can build toolchains that run natively under Windows/Cygwin
25 - so we can build toolchains that generate code for Windows/Win32
28 - so we can build toolchains that run natively under Windows/Win32
29 (without requiring Cygwin)
35 - check whether we can use newlib under uClinux (?)