Mercurialcrosstool-ng / file revision
summary | shortlog | changelog | graph | tags | branches | files | changeset | file | latest | revisions | annotate | diff | raw | help
scripts/showTuple.sh.in
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Mon Feb 21 23:39:46 2011 +0100 (2011-02-21)
changeset 2312 8b9938edd3d8
child 2468 90595d1c1017
permissions -rw-r--r--
libc/glibc: add fortify option

By default, recent versions of glibc and eglibc will build some
functions that take format strings (eg. printf, syslog...) with
run-time checks against some format string attacks. This is
called a fortified build.

Unfortunately, this fails somehow while building the instrumented
version of syslog, with some kind of circular dependency...

Disable fortified builds by default, and hide the enabling option
behind EXPERIMENTAL for daring users...

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr> 
     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
crosstool-ng