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 diff -durN duma_2_5_12.orig/Makefile duma_2_5_12/Makefile
2 --- duma_2_5_12.orig/Makefile 2007-08-17 09:34:25.000000000 +0200
3 +++ duma_2_5_12/Makefile 2007-09-07 21:50:04.000000000 +0200
16 createconf$(EXEPOSTFIX): createconf.o
17 - $(RMFORCE) createconf$(EXEPOSTFIX)
18 - $(CC) $(CFLAGS) $(DUMA_OPTIONS) createconf.o -o createconf$(EXEPOSTFIX)
19 + $(HOSTCC) $(HOSTCFLAGS) $(DUMA_OPTIONS) createconf.o -o createconf$(EXEPOSTFIX)
21 tstheap$(EXEPOSTFIX): libduma.a tstheap.o
22 - $(RMFORCE) tstheap$(EXEPOSTFIX)
24 # define rules how to build objects for createconf
27 - $(CC) $(CFLAGS) $(DUMA_OPTIONS) -c createconf.c -o $@
28 + $(HOSTCC) $(HOSTCFLAGS) $(DUMA_OPTIONS) -c createconf.c -o $@