scripts/build/arch/arm.sh
author Yann Diorcet <diorcet.yann@gmail.com>
Mon Nov 19 21:45:09 2012 +0100 (2012-11-19)
changeset 3121 5016315d88ba
parent 1597 fa8f3ab724f9
child 3158 1161ea79915b
permissions -rw-r--r--
binutils/binutils: simplify gold dependencies

In preparation of adding a new kernel-type, Yann D. came up
with a change in semantic on binutils/gold availability.

So far, it was architectures' responsibility to declare that
they did support binutils/gold or not. It makes much more sense
that binutils/gold declares its own availability depending on
the current architecture; after all, architectures have no way
to know wether gold supports them, while gold does know it.

Signed-off-by:Yann Diorcet <diorcet.yann@gmail.com>
[yann.morin.1998@free.fr: split up original patch for self-contained changes]
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Message-Id: <d3d1d51f399e6d2c1163.1353320546@macbook-smorlat.local>
Patchwork-Id: 199971
     1 # Compute ARM-specific values
     2 
     3 CT_DoArchTupleValues() {
     4     # The architecture part of the tuple:
     5     CT_TARGET_ARCH="${CT_ARCH}${target_endian_eb}"
     6 
     7     # The system part of the tuple:
     8     case "${CT_LIBC},${CT_ARCH_ARM_EABI}" in
     9         *glibc,y)   CT_TARGET_SYS=gnueabi;;
    10         uClibc,y)   CT_TARGET_SYS=uclibcgnueabi;;
    11         *,y)        CT_TARGET_SYS=eabi;;
    12     esac
    13 
    14     # Set the default instruction set mode
    15     case "${CT_ARCH_ARM_MODE}" in
    16         arm)    ;;
    17         thumb)
    18             CT_ARCH_CC_CORE_EXTRA_CONFIG="--with-mode=thumb"
    19             CT_ARCH_CC_EXTRA_CONFIG="--with-mode=thumb"
    20 #            CT_ARCH_TARGET_CFLAGS="-mthumb"
    21             ;;
    22     esac
    23 
    24     if [ "${CT_ARCH_ARM_INTERWORKING}" = "y" ]; then
    25         CT_ARCH_TARGET_CFLAGS+=" -mthumb-interwork"
    26     fi
    27 }