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 Index: binutils-2.19.51.0.5/ld/ld.texinfo
2 ===================================================================
3 --- binutils-2.19.51.0.5.orig/ld/ld.texinfo
4 +++ binutils-2.19.51.0.5/ld/ld.texinfo
5 @@ -2036,8 +2036,9 @@ This linker can create the new dynamic t
6 systems may not understand them. If you specify
7 @option{--enable-new-dtags}, the dynamic tags will be created as needed.
8 If you specify @option{--disable-new-dtags}, no new dynamic tags will be
9 -created. By default, the new dynamic tags are not created. Note that
10 -those options are only available for ELF systems.
11 +created. On Gentoo, by default, the new dynamic tags are created (this
12 +differs from upstream behaviour). Note that those options are only
13 +available for ELF systems.
15 @kindex --hash-size=@var{number}
16 @item --hash-size=@var{number}