scripts/showTuple.sh.in
author "Yann E. MORIN" <yann.morin.1998@free.fr>
Wed May 09 18:17:17 2012 +0200 (2012-05-09)
branch1.15
changeset 3002 56e4a47dcf88
parent 2468 90595d1c1017
child 3141 d8bd17248789
permissions -rw-r--r--
cc/gcc: do not build manuals in parallel

Reported-by: Benoît Thébaudeau <benoit.thebaudeau@advansee.com>
Reported-by: Johannes Stezenbach <js@sig21.net>
Tested-by: Johannes Stezenbach <js@sig21.net>
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
(transplanted from c800b7d6a50c267c3e0a64829da4b082e260deff)
     1 #!@@CT_bash@@
     2 
     3 # What we need:
     4 #  - the .config file
     5 
     6 # Parse the tools' paths configuration
     7 . "${CT_LIB_DIR}/paths.sh"
     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