config/libc/glibc.in
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Mon Mar 28 01:05:18 2011 +0200 (2011-03-28)
changeset 2362 0888065f8c4d
parent 2267 7af68e6083aa
child 2438 2ba5655f6297
permissions -rw-r--r--
cc/gcc: cleanup the _or_later logic

So far, we've had a version always select appropriate _or_later option,
which in turn would select all previous _or_later options.

Because the dependencies on companion libs were cumulative, that was
working OK. But the upcoming 4.6 will no longer depend on libelf, so
we can't keep the cumulative scheme we've been using so far.

Have each release family select the corresponding dependencies, instead
of relying on selecting previous _or_later.

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
yann@448
     1
# glibc options
bartvdrmeulen@2017
     2
# depends on ! MINGW32 && ! BARE_METAL && ARCH_USE_MMU
yann@448
     3
yann@922
     4
config LIBC_glibc
yann@922
     5
    select LIBC_SUPPORT_NPTL
yann@922
     6
    help
yann@922
     7
      The de-facto standard for Linux distributions.
yann@922
     8
      Feature-rich, but large...  Most usefull for desktop-like systems.
yann@852
     9
yann@448
    10
choice
yann@448
    11
    bool
yann@1760
    12
    prompt "Retrieval method"
yann@1760
    13
    default LIBC_GLIBC_TARBALL
yann@1760
    14
yann@1760
    15
config LIBC_GLIBC_TARBALL
yann@1760
    16
    bool
yann@1760
    17
    prompt "Released tarball"
yann@1760
    18
    help
yann@1760
    19
      Until end of Februrary 2009, there was no tarball for glibc releases
yann@1760
    20
      2.8 and later. This was intentional.
yann@1760
    21
      
yann@1760
    22
      Then, all of a sudden, tarballs for those releases have appeared at the
yann@1760
    23
      traditional download place (ftp.gnu.org).
yann@1760
    24
      
yann@1760
    25
      Some of the glibc people argue that fixes are committed to the maintenance
yann@1760
    26
      branch, and thus it is the best plac e to retrieve the glibc from.
yann@1760
    27
      On the other hand, it might be preferable to always generate a toolchain
yann@1760
    28
      using a known code-base, so the toolchain can be reproducible.
yann@1760
    29
      
yann@1760
    30
      For version prior to 2.8, tarballs were readily available.
yann@1760
    31
      
yann@1760
    32
      If you want your toolchain to really be reproducible, say 'Y' here.
yann@1760
    33
      If you can live with a moving code-base, look at the other choice
yann@1760
    34
      entries, below.
yann@1760
    35
yann@1760
    36
endchoice
yann@1760
    37
yann@1760
    38
choice
yann@1760
    39
    bool
yann@448
    40
    prompt "glibc version"
yann@1535
    41
# Don't remove next line
yann@1535
    42
# CT_INSERT_VERSION_BELOW
yann@448
    43
heiko@2235
    44
config LIBC_GLIBC_V_2_12_2
heiko@2235
    45
    bool
heiko@2235
    46
    prompt "2.12.2 (EXPERIMENTAL)"
heiko@2235
    47
    depends on EXPERIMENTAL
heiko@2235
    48
heiko@2235
    49
config LIBC_GLIBC_V_2_12_1
heiko@2235
    50
    bool
heiko@2235
    51
    prompt "2.12.1 (EXPERIMENTAL)"
heiko@2235
    52
    depends on EXPERIMENTAL
heiko@2235
    53
yann@1758
    54
config LIBC_GLIBC_V_2_11_1
yann@1758
    55
    bool
yann@1758
    56
    prompt "2.11.1 (EXPERIMENTAL)"
yann@1758
    57
    depends on EXPERIMENTAL
yann@1758
    58
yann@1758
    59
config LIBC_GLIBC_V_2_11
yann@1758
    60
    bool
yann@1758
    61
    prompt "2.11 (EXPERIMENTAL)"
yann@1758
    62
    depends on EXPERIMENTAL
yann@1758
    63
bryanhundven@2237
    64
config LIBC_GLIBC_V_2_10_1
yann@1625
    65
    bool
yann@1625
    66
    prompt "2.10.1 (EXPERIMENTAL)"
yann@1625
    67
    depends on EXPERIMENTAL
yann@1625
    68
    select LIBC_GLIBC_USE_PORTS
yann@1625
    69
bryanhundven@2237
    70
config LIBC_GLIBC_V_2_9
yann@448
    71
    bool
yann@1534
    72
    prompt "2.9"
yann@448
    73
bryanhundven@2237
    74
config LIBC_GLIBC_V_2_8
yann@1114
    75
    bool
yann@1260
    76
    prompt "2.8"
yann@1114
    77
bryanhundven@2237
    78
config LIBC_GLIBC_V_2_7
yann@1114
    79
    bool
yann@1615
    80
    prompt "2.7 (OBSOLETE)"
yann@1615
    81
    depends on OBSOLETE
yann@1534
    82
bryanhundven@2237
    83
config LIBC_GLIBC_V_2_6_1
yann@1534
    84
    bool
yann@1615
    85
    prompt "2.6.1 (OBSOLETE)"
yann@1615
    86
    depends on OBSOLETE
yann@1534
    87
bryanhundven@2237
    88
config LIBC_GLIBC_V_2_6
yann@1534
    89
    bool
yann@1615
    90
    prompt "2.6 (OBSOLETE)"
yann@1615
    91
    depends on OBSOLETE
yann@1534
    92
bryanhundven@2237
    93
config LIBC_GLIBC_V_2_5_1
yann@1534
    94
    bool
yann@1615
    95
    prompt "2.5.1 (OBSOLETE)"
yann@1615
    96
    depends on OBSOLETE
yann@2315
    97
    select LIBC_SUPPORT_LINUXTHREADS
yann@1534
    98
bryanhundven@2237
    99
config LIBC_GLIBC_V_2_5
yann@1534
   100
    bool
yann@1615
   101
    prompt "2.5 (OBSOLETE)"
yann@1615
   102
    depends on OBSOLETE
yann@2315
   103
    select LIBC_SUPPORT_LINUXTHREADS
yann@1534
   104
yann@448
   105
endchoice
yann@448
   106
yann@448
   107
config LIBC_VERSION
yann@448
   108
    string
yann@1535
   109
# Don't remove next line
yann@1535
   110
# CT_INSERT_VERSION_STRING_BELOW
heiko@2235
   111
    default "2.12.2" if LIBC_GLIBC_V_2_12_2
heiko@2235
   112
    default "2.12.1" if LIBC_GLIBC_V_2_12_1
yann@1758
   113
    default "2.11.1" if LIBC_GLIBC_V_2_11_1
yann@1758
   114
    default "2.11" if LIBC_GLIBC_V_2_11
bryanhundven@2237
   115
    default "2.10.1" if LIBC_GLIBC_V_2_10_1
bryanhundven@2237
   116
    default "2.9" if LIBC_GLIBC_V_2_9
bryanhundven@2237
   117
    default "2.8" if LIBC_GLIBC_V_2_8
bryanhundven@2237
   118
    default "2.7" if LIBC_GLIBC_V_2_7
bryanhundven@2237
   119
    default "2.6.1" if LIBC_GLIBC_V_2_6_1
bryanhundven@2237
   120
    default "2.6" if LIBC_GLIBC_V_2_6
bryanhundven@2237
   121
    default "2.5.1" if LIBC_GLIBC_V_2_5_1
bryanhundven@2237
   122
    default "2.5" if LIBC_GLIBC_V_2_5