arch/x86/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 383 f00eb97ff649
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 x86-specific values
yann@383
     2
yann@383
     3
# This one really need a little love! :-(
yann@383
     4
yann@383
     5
CT_DoArchValues() {
yann@383
     6
    # The architecture part of the tuple:
yann@383
     7
    arch="${CT_ARCH_ARCH}"
yann@383
     8
    [ -z "${arch}" ] && arch="${CT_ARCH_TUNE}"
yann@383
     9
    case "${arch}" in
yann@383
    10
        nocona|athlon*64|k8|athlon-fx|opteron)
yann@383
    11
            CT_DoError "Architecture is x86 (32-bit) but selected processor is \"${arch}\" (64-bit)";;
yann@383
    12
        "")                           CT_TARGET_ARCH=i386;;
yann@383
    13
        i386|i486|i586|i686)          CT_TARGET_ARCH="${arch}";;
yann@383
    14
        winchip*)                     CT_TARGET_ARCH=i486;;
yann@383
    15
        pentium|pentium-mmx|c3*)      CT_TARGET_ARCH=i586;;
yann@383
    16
        pentiumpro|pentium*|athlon*)  CT_TARGET_ARCH=i686;;
yann@383
    17
        *)                            CT_TARGET_ARCH=i586;;
yann@383
    18
    esac
yann@383
    19
yann@387
    20
    # The kernel ARCH:
yann@387
    21
    CT_KERNEL_ARCH=i386
yann@383
    22
}