scripts/showTuple.sh.in
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Sat Dec 19 12:44:21 2009 +0100 (2009-12-19)
branch1.5
changeset 1706 5360c810222d
child 2468 90595d1c1017
permissions -rw-r--r--
scripts: check for, and warn about an unset CT_PREFIX_DIR

The user shall provide a directory to install the toolchain into.
If he/she does not, this is an error, and shall be detected properly,
rather than relying on failure down the road.

Thanks to "Pedro I. Sanchez" <psanchez@colcan.ca> for pointing out
the issue:
http://sourceware.org/ml/crossgcc/2009-12/msg00011.html
(transplanted from e94f4ffddd1d07b3841160db71694cd19fda6b03)
yann@1336
     1
#!@@CT_bash@@
yann@1336
     2
yann@1336
     3
# What we need:
yann@1336
     4
#  - the .config file
yann@1336
     5
yann@1336
     6
# Parse the tools' paths configuration
yann@1336
     7
. "${CT_LIB_DIR}/paths.mk"
yann@1336
     8
yann@1336
     9
# We'll need the stdout later, save it
yann@1336
    10
exec 7>&1
yann@1336
    11
yann@1336
    12
# Parse the common functions
yann@1336
    13
. "${CT_LIB_DIR}/scripts/functions"
yann@1336
    14
yann@1336
    15
# Don't care about any log file
yann@1336
    16
exec >/dev/null
yann@1336
    17
rm -f "${tmp_log_file}"
yann@1336
    18
yann@1336
    19
# Parse the configuration file
yann@1336
    20
. .config
yann@1336
    21
yann@1336
    22
# Parse architecture and kernel specific functions
yann@1336
    23
. "${CT_LIB_DIR}/scripts/build/arch/${CT_ARCH}.sh"
yann@1336
    24
. "${CT_LIB_DIR}/scripts/build/kernel/${CT_KERNEL}.sh"
yann@1336
    25
yann@1336
    26
# Build CT_TARGET
yann@1336
    27
CT_DoBuildTargetTuple
yann@1336
    28
yann@1336
    29
# All this for this single echo... :-( Sigh, I'll have to re-arrange things...
yann@1336
    30
echo "${CT_TARGET}" >&7