config/companion_tools.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
parent 1729 dd72fa745318
child 2285 7d1e018167b5
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 # Companion tools config options
     2 
     3 if EXPERIMENTAL
     4 
     5 menu "Companion tools"
     6 
     7 comment "READ HELP before you say 'Y' below !!!"
     8 config COMP_TOOLS
     9     bool
    10     prompt "Build some companion tools"
    11     help
    12       Crosstool-NG relies on some external tools to be recent enough, namely:
    13         m4 >= 1.4.12
    14         autoconf >= 2.63
    15         automake >= 1.10.2
    16         libtool >= 2.2.4
    17       
    18       If your system has older versions, we can build them for you,
    19       but you are strongly encouraged to update your system instead!
    20 
    21 if COMP_TOOLS
    22 
    23 config COMP_TOOLS_m4
    24     bool
    25     prompt "m4"
    26 
    27 config COMP_TOOLS_autoconf
    28     bool
    29     prompt "autoconf"
    30 
    31 config COMP_TOOLS_automake
    32     bool
    33     prompt "automake"
    34 
    35 config COMP_TOOLS_libtool
    36     bool
    37     prompt "libtool"
    38 
    39 endif
    40 
    41 endmenu
    42 
    43 endif