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 Description: correct where ld scripts are installed
2 Author: Chris Chimelis <chris@debian.org>
4 --- binutils-2.16.91.0.1/ld/Makefile.am
5 +++ binutils-2.16.91.0.1/ld/Makefile.am
7 # We put the scripts in the directory $(scriptdir)/ldscripts.
8 # We can't put the scripts in $(datadir) because the SEARCH_DIR
9 # directives need to be different for native and cross linkers.
10 -scriptdir = $(tooldir)/lib
11 +scriptdir = $(libdir)
14 EMULATION_OFILES = @EMULATION_OFILES@
15 --- binutils-2.16.91.0.1/ld/Makefile.in
16 +++ binutils-2.16.91.0.1/ld/Makefile.in
18 # We put the scripts in the directory $(scriptdir)/ldscripts.
19 # We can't put the scripts in $(datadir) because the SEARCH_DIR
20 # directives need to be different for native and cross linkers.
21 -scriptdir = $(tooldir)/lib
22 +scriptdir = $(libdir)
23 BASEDIR = $(srcdir)/..
24 BFDDIR = $(BASEDIR)/bfd
25 INCDIR = $(BASEDIR)/include