scripts/showTuple.sh.in
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Fri Oct 08 23:37:12 2010 +0200 (2010-10-08)
branch1.8
changeset 2150 f97a8ad2b172
child 2468 90595d1c1017
permissions -rw-r--r--
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 #!@@CT_bash@@
     2 
     3 # What we need:
     4 #  - the .config file
     5 
     6 # Parse the tools' paths configuration
     7 . "${CT_LIB_DIR}/paths.mk"
     8 
     9 # We'll need the stdout later, save it
    10 exec 7>&1
    11 
    12 # Parse the common functions
    13 . "${CT_LIB_DIR}/scripts/functions"
    14 
    15 # Don't care about any log file
    16 exec >/dev/null
    17 rm -f "${tmp_log_file}"
    18 
    19 # Parse the configuration file
    20 . .config
    21 
    22 # Parse architecture and kernel specific functions
    23 . "${CT_LIB_DIR}/scripts/build/arch/${CT_ARCH}.sh"
    24 . "${CT_LIB_DIR}/scripts/build/kernel/${CT_KERNEL}.sh"
    25 
    26 # Build CT_TARGET
    27 CT_DoBuildTargetTuple
    28 
    29 # All this for this single echo... :-( Sigh, I'll have to re-arrange things...
    30 echo "${CT_TARGET}" >&7