scripts/showTuple.sh.in
author "Yann E. MORIN" <yann.morin.1998@free.fr>
Sun Nov 25 18:22:38 2012 +0100 (2012-11-25)
changeset 3133 36aa2ae92c29
parent 2468 90595d1c1017
child 3141 d8bd17248789
permissions -rw-r--r--
cc/gcc: do not print 'core' or 'final'

In gcc-'s core and final passes, do not print 'core' or 'final' in
log messages. We already print it in step messages.

Also, as we use the core backend to build the bare-metal final gcc,
it can be disturbing to read 'core' while we're in fact in 'final'.

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
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@2838
     7
. "${CT_LIB_DIR}/paths.sh"
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@2468
    20
. .config.2
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