Mercurialcrosstool-ng / file revision
summary | shortlog | changelog | graph | tags | branches | files | changeset | file | latest | revisions | annotate | diff | raw | help
config/libc/glibc.in
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Fri Oct 02 00:04:24 2009 +0200 (2009-10-02)
changeset 1557 a576367cac44
parent 1535 073d351bdcd3
child 1558 d2b746e94197
permissions -rw-r--r--
libc/glibc: remove dead code

The option to retrieve snapshots is already handled by
the generic 'specific date' and 'use latest' entries.
No need for a special case, as there's no code for it. 
     1 # glibc options

     2 # depends on ! BARE_METAL && ARCH_USE_MMU

     3 

     4 config LIBC_glibc

     5     select LIBC_SUPPORT_NPTL

     6     select LIBC_SUPPORT_LINUXTHREADS

     7     help

     8       The de-facto standard for Linux distributions.

     9       Feature-rich, but large...  Most usefull for desktop-like systems.

    10 

    11 choice

    12     bool

    13     prompt "glibc version"

    14 # Don't remove next line

    15 # CT_INSERT_VERSION_BELOW

    16 

    17 config LIBC_V_2_9

    18     bool

    19     prompt "2.9"

    20     select LIBC_GLIBC_2_8_or_later

    21 

    22 config LIBC_V_2_8

    23     bool

    24     prompt "2.8"

    25     select LIBC_GLIBC_2_8_or_later

    26 

    27 config LIBC_V_2_7

    28     bool

    29     prompt "2.7"

    30 

    31 config LIBC_V_2_6_1

    32     bool

    33     prompt "2.6.1"

    34 

    35 config LIBC_V_2_6

    36     bool

    37     prompt "2.6"

    38 

    39 config LIBC_V_2_5_1

    40     bool

    41     prompt "2.5.1"

    42 

    43 config LIBC_V_2_5

    44     bool

    45     prompt "2.5"

    46 

    47 config LIBC_V_2_3_6

    48     bool

    49     prompt "2.3.6 (OBSOLETE)"

    50     depends on OBSOLETE

    51 

    52 config LIBC_V_LATEST

    53     bool

    54     prompt "'latest' snapshot (EXPERIMENTAL)"

    55     depends on EXPERIMENTAL

    56 

    57 config LIBC_V_date

    58     bool

    59     prompt "<specific date> (EXPERIMENTAL)"

    60     depends on EXPERIMENTAL

    61 

    62 endchoice

    63 

    64 config LIBC_VERSION

    65     string

    66     prompt "Enter date (YYYYMMDD)" if LIBC_V_date

    67 # Don't remove next line

    68 # CT_INSERT_VERSION_STRING_BELOW

    69     default "2.9" if LIBC_V_2_9

    70     default "2.8" if LIBC_V_2_8

    71     default "2.7" if LIBC_V_2_7

    72     default "2.6.1" if LIBC_V_2_6_1

    73     default "2.6" if LIBC_V_2_6

    74     default "2.5.1" if LIBC_V_2_5_1

    75     default "2.5" if LIBC_V_2_5

    76     default "2.3.6" if LIBC_V_2_3_6

    77     default "latest" if LIBC_V_LATEST

    78 

    79 config LIBC_GLIBC_2_8_or_later

    80     bool

    81     default n

    82 

    83 choice

    84     bool

    85     prompt "Retrieval method"

    86     default LIBC_GLIBC_TARBALL

    87 

    88 config LIBC_GLIBC_TARBALL

    89     bool

    90     prompt "Released tarball"

    91     depends on ! LIBC_GLIBC_2_8_or_later || ! ( LIBC_GLIBC_USE_PORTS || ( LIBC_ADDONS_LIST != "" ) )

    92     help

    93       Until end of Februrary 2009, there was no tarball for glibc releases

    94       2.8 and later. This was intentional.

    95       

    96       Then, all of a sudden, tarballs for those releases have appeared at the

    97       traditional download place (ftp.gnu.org).

    98       

    99       Some of the glibc people argue that fixes are committed to the maintenance

   100       branch, and thus it is the best plac e to retrieve the glibc from.

   101       On the other hand, it might be preferable to always generate a toolchain

   102       using a known code-base, so the toolchain can be reproducible.

   103       

   104       For version prior to 2.8, tarballs were readily available.

   105       

   106       If you want your toolchain to really be reproducible, say 'Y' here.

   107       If you can live with a moving code-base, look at the other choice

   108       entries, below.

   109 

   110 config LIBC_GLIBC_CVS

   111     bool

   112     prompt "CVS checkout"

   113     help

   114       See the help for the entry "Released tarball", above.

   115       

   116       If you can live with a moving code-base, say 'Y' here.

   117       If you want your toolchain to really be reproducible, look at the

   118       choice entry "Released tarball from FTP", above.

   119 

   120 if LIBC_GLIBC_CVS

   121 

   122 config LIBC_GLIBC_CVS_date

   123     string

   124     prompt "checkout as of date"

   125     default ""

   126     help

   127       The date, in ISO-8601 format, at which to check out the repository.

   128 

   129 endif #  LIBC_GLIBC_CVS

   130 

   131 endchoice
crosstool-ng