yann@787: # eglibc options yann@787: yann@787: choice yann@787: bool yann@787: prompt "eglibc version" yann@787: yann@787: config EGLIBC_V_TRUNK yann@787: bool yann@787: prompt "'trunk'" yann@787: help yann@787: Selecting this will export the trunk of the eglibc subversion repository. yann@787: yann@787: config EGLIBC_V_2_5 yann@787: bool yann@787: prompt "2.5" yann@787: yann@787: config EGLIBC_V_2_6 yann@787: bool yann@787: prompt "2.6" yann@787: yann@787: config EGLIBC_V_2_7 yann@787: bool yann@787: prompt "2.7" yann@787: yann@787: config EGLIBC_V_2_8 yann@787: bool yann@787: prompt "2.8" yann@787: yann@787: # CT_INSERT_VERSION_ABOVE yann@787: # Don't remove above line! yann@787: endchoice yann@787: yann@787: config LIBC_VERSION yann@787: string yann@787: default "trunk" if EGLIBC_V_TRUNK yann@787: default "2_5" if EGLIBC_V_2_5 yann@787: default "2_6" if EGLIBC_V_2_6 yann@787: default "2_7" if EGLIBC_V_2_7 yann@787: default "2_8" if EGLIBC_V_2_8 yann@787: # CT_INSERT_VERSION_STRING_ABOVE yann@787: # Don't remove above line! yann@787: yann@787: config EGLIBC_REVISION yann@787: string yann@787: prompt "Revision to use" yann@787: default "HEAD" yann@787: help yann@787: Enter the revision of trunk you want to use. yann@787: Default is HEAD. yann@787: yann@787: A revision argument can be one of: yann@787: NUMBER revision number yann@787: '{' DATE '}' revision at start of the date (*) yann@787: 'HEAD' latest in repository yann@787: yann@787: (*) If you want to use a date, please use ISO-8601 formats if yann@787: at all possible. yann@787: yann@787: config EGLIBC_CHECKOUT yann@787: bool yann@787: prompt "checkout instead of export" yann@787: default y if EGLIBC_V_TRUNK yann@787: default n if ! EGLIBC_V_TRUNK yann@787: help yann@787: By default, the eglibc download will be an export of the subversion yann@787: repository. If you say 'y' here, then the repository will instead be yann@787: checked-out, so that you can update it later. yann@787: yann@787: Note that crosstool-NG will *not* update your working copy, you will yann@787: have to do that yourself. yann@787: yann@787: config LIBC_EGLIBC_EXTRA_CONFIG yann@787: string yann@787: prompt "eglibc extra config" yann@787: default "" yann@787: help yann@787: Extra flags to pass onto ./configure when configuring eglibc. yann@787: yann@787: Eg.: --enable-static-nss yann@787: yann@787: config LIBC_EGLIBC_EXTRA_CFLAGS yann@787: string yann@787: prompt "eglibc extra target CFLAGS" yann@787: default "" yann@787: help yann@787: Extra target CFLAGS to use when building eglibc. yann@787: yann@787: config LIBC_EXTRA_CC_ARGS yann@787: string yann@787: prompt "gcc extra flags" yann@787: default "" yann@787: help yann@787: Extra flags to pass gcc when building eglibc. yann@787: yann@787: Seldom used, except for sparc64 which seems to need the flag -64 yann@787: to be passed onto gcc. yann@787: yann@787: config LIBC_EGLIBC_USE_PORTS yann@787: bool yann@787: prompt "Use the ports addon" yann@787: default n yann@787: help yann@787: The ports addon contains some architecture ports that are not available yann@787: in the official glibc distribution. yann@787: yann@787: For example, this is the case for ARM with glibc >= 2.4 yann@787: yann@787: Say n only if you're sure that your architecture is in the official yann@787: glibc distribution for your chosen version. yann@787: yann@787: config LIBC_ADDONS yann@787: bool yann@787: prompt "Pass extra addons list" yann@787: default n yann@787: help yann@787: If you say Y here, you'll be able to give the list of addons you want to yann@787: include in your C library. yann@787: yann@787: config LIBC_ADDONS_LIST yann@787: string yann@787: prompt "Extra addons" yann@787: default "" yann@787: depends on LIBC_ADDONS yann@787: help yann@787: Extra addons to include in eglibc. Space separated list. yann@787: yann@787: You need to specify neither linuxthreads nor nptl, as they are added yann@787: automagically for you depending on the threading model you choosed yann@787: earlier. yann@787: yann@787: Eg.: crypt (for very old glibces)