config/libc/glibc.in
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 852 c17bb66e2aa5
child 922 3f0456891349
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@448
     1
# glibc options
yann@448
     2
yann@852
     3
comment "glibc specific options"
yann@852
     4
yann@448
     5
choice
yann@448
     6
    bool
yann@448
     7
    prompt "glibc version"
yann@448
     8
yann@448
     9
config LIBC_V_2_3_6
yann@448
    10
    bool
yann@448
    11
    prompt "2.3.6 (OBSOLETE)"
yann@448
    12
    depends on OBSOLETE
yann@448
    13
yann@448
    14
config LIBC_V_2_5
yann@448
    15
    bool
yann@448
    16
    prompt "2.5"
yann@448
    17
yann@448
    18
config LIBC_V_2_5_1
yann@448
    19
    bool
yann@448
    20
    prompt "2.5.1"
yann@448
    21
yann@448
    22
config LIBC_V_2_6
yann@448
    23
    bool
yann@448
    24
    prompt "2.6"
yann@448
    25
yann@448
    26
config LIBC_V_2_6_1
yann@448
    27
    bool
yann@448
    28
    prompt "2.6.1"
yann@448
    29
yann@448
    30
config LIBC_V_2_7
yann@448
    31
    bool
yann@448
    32
    prompt "2.7"
yann@448
    33
yann@448
    34
# CT_INSERT_VERSION_ABOVE
yann@448
    35
# Don't remove above line!
yann@865
    36
yann@865
    37
config LIBC_V_LATEST
yann@865
    38
    bool
yann@865
    39
    prompt "'latest' snapshot (EXPERIMENTAL)"
yann@865
    40
    depends on EXPERIMENTAL
yann@865
    41
yann@865
    42
config LIBC_V_date
yann@865
    43
    bool
yann@865
    44
    prompt "<specific date> (EXPERIMENTAL)"
yann@865
    45
    depends on EXPERIMENTAL
yann@865
    46
yann@448
    47
endchoice
yann@448
    48
yann@448
    49
config LIBC_VERSION
yann@448
    50
    string
yann@710
    51
    prompt "Enter date (YYYYMMDD)" if LIBC_V_date
yann@710
    52
    default "latest" if LIBC_V_LATEST
yann@448
    53
    default "2.3.6" if LIBC_V_2_3_6
yann@448
    54
    default "2.4" if LIBC_V_2_4
yann@448
    55
    default "2.5" if LIBC_V_2_5
yann@448
    56
    default "2.5.1" if LIBC_V_2_5_1
yann@448
    57
    default "2.6" if LIBC_V_2_6
yann@448
    58
    default "2.6.1" if LIBC_V_2_6_1
yann@448
    59
    default "2.7" if LIBC_V_2_7
yann@448
    60
# CT_INSERT_VERSION_STRING_ABOVE
yann@448
    61
# Don't remove above line!
yann@448
    62
yann@448
    63
# Please note: This is not used for now (no sh support).
yann@448
    64
config LIBC_GLIBC_CONFIGPARMS
yann@448
    65
    string
yann@808
    66
#    prompt "Extra config params (READ HELP)"
yann@448
    67
    default "" if ARCH != "sh3" && ARCH != "sh4"
yann@448
    68
    default "no-z-defs=yes" if ARCH = "sh3" || ARCH = "sh4"
yann@448
    69
    help
yann@448
    70
      Some architectures need to set options in the file configparms.
yann@448
    71
      This is the case for sh3/4, which really need to set configparms as of
yann@448
    72
      gcc-3.4/glibc-2.3.2.
yann@448
    73
yann@448
    74
      Unless you are building a toolchain for sh3/4, you should leave that empty.
yann@448
    75
yann@448
    76
      Note: this is awkward, doesn't work well if you need more than one
yann@448
    77
            line in configparms