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>
Tue Jan 03 22:57:25 2012 +0100 (2012-01-03)
changeset 2936 2dfea349d307
parent 2468 90595d1c1017
child 3141 d8bd17248789
permissions -rw-r--r--
cc/gcc: build core compilers for canadian

Currently, we rely on an existing external cross-compiler targetting
the target, to build the C library.

This can pause quite a few problems if that compiler is different from
the one we are building, because it could introduce some ABI issues.

This patch removes this dependency, by building the core compilers
as we do for standard cross, and also by building the binutils and
gcc, for running on the build machine.

This means we no longer need to offer the cross-sompiler selection in
the menuconfig.

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.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
crosstool-ng