config/libc/glibc.in
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Thu Mar 26 18:58:13 2009 +0000 (2009-03-26)
changeset 1269 17e37102a037
parent 1260 777153645ab8
child 1314 34d1b285c5db
permissions -rw-r--r--
Merge r1432:1437 from /branches/newlib into /trunk :
- under bare-metal, the user is responsible for providing a gdbserver stub (r1433)
- install a CT_TARGET-cc -> CT_TARGET-gcc symlink for the core gcc (r1434)
- allow broader dependency in generated config files (r1435, r1436)
- prepare C library menuconfig for using a C library under bare-metal (r1437)

/trunk/scripts/build/cc/gcc.sh | 4 4 0 0 ++++
/trunk/config/debug/gdb.in | 5 5 0 0 +++++
/trunk/config/libc/glibc.in | 1 1 0 0 +
/trunk/config/libc/uClibc.in | 1 1 0 0 +
/trunk/config/libc/eglibc.in | 2 1 1 0 +-
/trunk/config/config.mk | 20 8 12 0 ++++++++------------
/trunk/config/arch/sh.in | 2 1 1 0 +-
/trunk/config/arch/ia64.in | 2 1 1 0 +-
/trunk/config/arch/powerpc64.in | 2 1 1 0 +-
/trunk/config/libc.in | 4 0 4 0 ----
10 files changed, 23 insertions(+), 20 deletions(-)
     1 # glibc options
     2 # depends on ! BARE_METAL
     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 
    15 config LIBC_V_2_3_6
    16     bool
    17     prompt "2.3.6 (OBSOLETE)"
    18     depends on OBSOLETE
    19 
    20 config LIBC_V_2_5
    21     bool
    22     prompt "2.5"
    23 
    24 config LIBC_V_2_5_1
    25     bool
    26     prompt "2.5.1"
    27 
    28 config LIBC_V_2_6
    29     bool
    30     prompt "2.6"
    31 
    32 config LIBC_V_2_6_1
    33     bool
    34     prompt "2.6.1"
    35 
    36 config LIBC_V_2_7
    37     bool
    38     prompt "2.7"
    39 
    40 config LIBC_V_2_8
    41     bool
    42     prompt "2.8"
    43 
    44 config LIBC_V_2_9
    45     bool
    46     prompt "2.9"
    47 
    48 # CT_INSERT_VERSION_ABOVE
    49 # Don't remove above line!
    50 
    51 config LIBC_V_LATEST
    52     bool
    53     prompt "'latest' snapshot (EXPERIMENTAL)"
    54     depends on EXPERIMENTAL
    55 
    56 config LIBC_V_date
    57     bool
    58     prompt "<specific date> (EXPERIMENTAL)"
    59     depends on EXPERIMENTAL
    60 
    61 endchoice
    62 
    63 config LIBC_VERSION
    64     string
    65     prompt "Enter date (YYYYMMDD)" if LIBC_V_date
    66     default "latest" if LIBC_V_LATEST
    67     default "2.3.6" if LIBC_V_2_3_6
    68     default "2.4" if LIBC_V_2_4
    69     default "2.5" if LIBC_V_2_5
    70     default "2.5.1" if LIBC_V_2_5_1
    71     default "2.6" if LIBC_V_2_6
    72     default "2.6.1" if LIBC_V_2_6_1
    73     default "2.7" if LIBC_V_2_7
    74     default "2.8" if LIBC_V_2_8
    75     default "2.9" if LIBC_V_2_9
    76 # CT_INSERT_VERSION_STRING_ABOVE
    77 # Don't remove above line!
    78 
    79 choice
    80     bool
    81     prompt "Retrieval method"
    82     default LIBC_GLIBC_TARBALL
    83 
    84 config LIBC_GLIBC_TARBALL
    85     bool
    86     prompt "Released tarball"
    87     help
    88       Until end of Februrary 2009, there was no tarball for glibc releases
    89       2.8 and later. This was intentional.
    90       
    91       Then, all of a sudden, tarballs for those releases have appeared at the
    92       traditional download place (ftp.gnu.org).
    93       
    94       Some of the glibc people argue that fixes are committed to the maintenance
    95       branch, and thus it is the best plac e to retrieve the glibc from.
    96       On the other hand, it might be preferable to always generate a toolchain
    97       using a known code-base, so the toolchain can be reproducible.
    98       
    99       For version prior to 2.8, tarballs were readily available.
   100       
   101       If you want your toolchain to really be reproducible, say 'Y' here.
   102       If you can live with a moving code-base, look at the other choice
   103       entries, below.
   104 
   105 config LIBC_GLIBC_CVS
   106     bool
   107     prompt "CVS checkout"
   108     help
   109       See the help for the entry "Released tarball", above.
   110       
   111       If you can live with a moving code-base, say 'Y' here.
   112       If you want your toolchain to really be reproducible, look at the
   113       choice entry "Released tarball from FTP", above.
   114 
   115 if LIBC_GLIBC_CVS
   116 
   117 config LIBC_GLIBC_CVS_date
   118     string
   119     prompt "checkout as of date"
   120     default ""
   121     help
   122       The date, in ISO-8601 format, at which to check out the repository.
   123 
   124 endif #  LIBC_GLIBC_CVS
   125 
   126 #config LIBC_GLIBC_SNAPSHOT
   127 #    bool
   128 #    prompt "Use latest nightly snapshot"
   129 #    help
   130 #      See the help for the entry "Released tarball", above.
   131 #      
   132 #      If you can live with a moving code-base, say 'Y' here.
   133 #      If you want your toolchain to really be reproducible, look at the
   134 #      choice entry "Released tarball from FTP", above.
   135 
   136 endchoice