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 Dec 12 21:41:16 2011 +0200 (2011-12-12)
branch1.13
changeset 2845 0dc9d4931246
parent 1336 bc8b9381f637
child 2838 822af73497bf
permissions -rw-r--r--
scripts: unset CONFIG_SITE

Some distributions (eg. openSUSE 12.1) systematically export
the CONFIG_SITE environment variable to point to a custom
script setting misc paths for ./configure.

This can, and does, break when cross-compiling for architectures
that are not supported by this script.

The simple workaround is to unset this variable.
NB: buildroot has a similar fix:
http://git.buildroot.org/buildroot/commit/?id=12c9f7dd6dee9c6029b4f9a12d6aac1516911ab4

Reported-by: Trevor Woerner <twoerner@gmail.com>
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
(transplanted from 21f4f28e60ec0342133086c9a51e7f0e5b181fb8) 
     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.2

    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