arch/arm/functions
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Tue Sep 23 14:48:10 2008 +0000 (2008-09-23)
changeset 872 fd4bf138f08f
parent 820 d43c250051c7
permissions -rw-r--r--
Bart De VOS pointed out that removing absolute paths from the libc linker scripts is plainly wrong.
It dates from dawn ages of the original crosstool code, and is not well explained. At that time, binutils might not understand the sysroot stuff, and it was necessary to remove absolute paths in that case.

/trunk/scripts/build/libc/glibc.sh | 14 2 12 0 ++------------
1 file changed, 2 insertions(+), 12 deletions(-)
yann@383
     1
# Compute ARM-specific values
yann@383
     2
yann@383
     3
CT_DoArchValues() {
yann@383
     4
    # The architecture part of the tuple:
yann@383
     5
    CT_TARGET_ARCH="${CT_ARCH}${target_endian_eb}"
yann@383
     6
yann@385
     7
    # The system part of the tuple:
yann@385
     8
    case "${CT_LIBC},${CT_ARCH_ARM_EABI}" in
yann@787
     9
        *glibc,y)   CT_TARGET_SYS=gnueabi;;
yann@385
    10
        uClibc,y)   CT_TARGET_SYS=uclibcgnueabi;;
yann@850
    11
        none,y)     CT_TARGET_SYS=eabi;;
yann@385
    12
    esac
yann@503
    13
yann@820
    14
    # In case we're EABI, do *not* specify any ABI!
yann@820
    15
    # which means, either we do not have an ABI specified, or we're not EABI.
yann@820
    16
    CT_TestOrAbort "Internal error: CT_ARCH_ABI should not be set for EABI build." -z "${CT_ARCH_ABI}" -o -z "${CT_ARCH_ARM_EABI}"
yann@383
    17
}