config/libc_glibc.in
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Sun Feb 17 22:08:06 2008 +0000 (2008-02-17)
changeset 431 8bde4c6ea47a
parent 352 caaeea0b3d51
permissions -rw-r--r--
Robert P. J. DAY says:

apparently, the patchset for gcc 4.2.1 applies properly to the
source for gcc 4.2.2 and gcc 4.2.3. so, if you want, you can simply
add support for those last two just by augmenting menuconfig and
adding a couple symlinks for those two directories. seems like a
cheap way to add a couple new versions.
yann@1
     1
# glibc options
yann@1
     2
yann@1
     3
choice
yann@1
     4
    bool
yann@1
     5
    prompt "glibc version"
yann@1
     6
yann@1
     7
config LIBC_V_2_3_6
yann@1
     8
    bool
yann@330
     9
    prompt "2.3.6 (OBSOLETE)"
yann@330
    10
    depends on OBSOLETE
yann@1
    11
yann@1
    12
config LIBC_V_2_5
yann@1
    13
    bool
yann@1
    14
    prompt "2.5"
yann@1
    15
yann@323
    16
config LIBC_V_2_5_1
yann@323
    17
    bool
yann@330
    18
    prompt "2.5.1"
yann@323
    19
yann@323
    20
config LIBC_V_2_6
yann@323
    21
    bool
yann@352
    22
    prompt "2.6"
yann@323
    23
yann@323
    24
config LIBC_V_2_6_1
yann@323
    25
    bool
yann@352
    26
    prompt "2.6.1"
yann@323
    27
yann@409
    28
config LIBC_V_2_7
yann@409
    29
    bool
yann@409
    30
    prompt "2.7"
yann@409
    31
    depends on EXPERIMENTAL
yann@409
    32
yann@1
    33
# CT_INSERT_VERSION_ABOVE
yann@22
    34
# Don't remove above line!
yann@1
    35
endchoice
yann@1
    36
yann@1
    37
config LIBC_VERSION
yann@1
    38
    string
yann@1
    39
    default "2.3.6" if LIBC_V_2_3_6
yann@1
    40
    default "2.4" if LIBC_V_2_4
yann@1
    41
    default "2.5" if LIBC_V_2_5
yann@323
    42
    default "2.5.1" if LIBC_V_2_5_1
yann@323
    43
    default "2.6" if LIBC_V_2_6
yann@323
    44
    default "2.6.1" if LIBC_V_2_6_1
yann@409
    45
    default "2.7" if LIBC_V_2_7
yann@1
    46
# CT_INSERT_VERSION_STRING_ABOVE
yann@1
    47
# Don't remove above line!
yann@1
    48
yann@1
    49
config LIBC_GLIBC_EXTRA_CONFIG
yann@1
    50
    string
yann@1
    51
    prompt "glibc extra config"
yann@1
    52
    default ""
yann@1
    53
    help
yann@1
    54
      Extra flags to pass onto ./configure when configuring glibc.
yann@1
    55
yann@1
    56
      Eg.: --enable-static-nss
yann@1
    57
yann@1
    58
config LIBC_GLIBC_EXTRA_CFLAGS
yann@1
    59
    string
yann@1
    60
    prompt "glibc extra target CFLAGS"
yann@1
    61
    default ""
yann@1
    62
    help
yann@1
    63
      Extra target CFLAGS to use when building glibc.
yann@1
    64
yann@1
    65
config LIBC_EXTRA_CC_ARGS
yann@1
    66
    string
yann@1
    67
    prompt "gcc extra flags"
yann@1
    68
    default ""
yann@1
    69
    help
yann@1
    70
      Extra flags to pass gcc when building glibc.
yann@1
    71
yann@1
    72
      Seldom used, except for sparc64 which seems to need the flag -64
yann@1
    73
      to be passed onto gcc.
yann@1
    74
yann@1
    75
# Please note: This is not used for now (no sh support).
yann@1
    76
config LIBC_GLIBC_CONFIGPARMS
yann@1
    77
    string
yann@1
    78
    prompt "Extra config params (READ HELP)"
yann@1
    79
    default "" if ARCH != "sh3" && ARCH != "sh4"
yann@1
    80
    default "no-z-defs=yes" if ARCH = "sh3" || ARCH = "sh4"
yann@1
    81
    help
yann@1
    82
      Some architectures need to set options in the file configparms.
yann@1
    83
      This is the case for sh3/4, which really need to set configparms as of
yann@1
    84
      gcc-3.4/glibc-2.3.2.
yann@1
    85
yann@1
    86
      Unless you are building a toolchain for sh3/4, you should leave that empty.
yann@1
    87
yann@1
    88
      Note: this is awkward, doesn't work well if you need more than one
yann@1
    89
            line in configparms
yann@1
    90
yann@16
    91
config LIBC_GLIBC_USE_PORTS
yann@16
    92
    bool
yann@16
    93
    prompt "Use the ports addon"
yann@136
    94
    default n
yann@16
    95
    help
yann@16
    96
      The ports addon contains some architecture ports that are not available
yann@16
    97
      in the official glibc distribution.
yann@16
    98
      
yann@16
    99
      For example, this is the case for ARM with glibc >= 2.4
yann@16
   100
      
yann@16
   101
      Say n only if you're sure that your architecture is in the official
yann@16
   102
      glibc distribution for your chosen version.
yann@16
   103
yann@1
   104
config LIBC_ADDONS
yann@1
   105
    bool
yann@1
   106
    prompt "Pass extra addons list"
yann@1
   107
    default n
yann@1
   108
    help
yann@1
   109
      If you say Y here, you'll be able to give the list of addons you want to
yann@1
   110
      include in your C library.
yann@1
   111
yann@1
   112
config LIBC_ADDONS_LIST
yann@1
   113
    string
yann@1
   114
    prompt "Extra addons"
yann@1
   115
    default ""
yann@16
   116
    depends on LIBC_ADDONS
yann@1
   117
    help
yann@142
   118
      Extra addons to include in glibc. Space separated list.
yann@142
   119
yann@142
   120
      You need to specify neither linuxthreads nor nptl, as they are added
yann@142
   121
      automagically for you depending on the threading model you choosed
yann@142
   122
      earlier.
yann@1
   123
      
yann@1
   124
      Eg.: crypt        (for very old glibces)