Add a patchset for glibc 2_9. Vampirised from the gentoo repository.

/trunk/patches/glibc/2_9/500-ppc-glibc-2.9-atomic.patch | 414 414 0 0 ++++++++++
/trunk/patches/glibc/2_9/140-regex-BZ9697.patch | 111 111 0 0 +++
/trunk/patches/glibc/2_9/190-queue-header-updates.patch | 89 89 0 0 ++
/trunk/patches/glibc/2_9/370-hppa_glibc-2.7-hppa-nptl-carlos.patch | 249 249 0 0 ++++++
/trunk/patches/glibc/2_9/450-alpha-glibc-2.5-no-page-header.patch | 32 32 0 0 +
/trunk/patches/glibc/2_9/270-ldbl-nexttowardf.patch | 68 68 0 0 ++
/trunk/patches/glibc/2_9/330-2.3.3-china.patch | 35 35 0 0 +
/trunk/patches/glibc/2_9/340-new-valencian-locale.patch | 120 120 0 0 +++
/trunk/patches/glibc/2_9/410-2.9-fnmatch.patch | 64 64 0 0 ++
/trunk/patches/glibc/2_9/350-2.4-undefine-__i686.patch | 47 47 0 0 +
/trunk/patches/glibc/2_9/160-i386-x86_64-revert-clone-cfi.patch | 53 53 0 0 +
/trunk/patches/glibc/2_9/420-dont-build-timezone.patch | 19 19 0 0 +
/trunk/patches/glibc/2_9/150-regex-BZ697.patch | 28 28 0 0 +
/trunk/patches/glibc/2_9/290-no-inline-gmon.patch | 38 38 0 0 +
/trunk/patches/glibc/2_9/280-section-comments.patch | 29 29 0 0 +
/trunk/patches/glibc/2_9/180-math-tests.patch | 72 72 0 0 ++
/trunk/patches/glibc/2_9/120-_nss_dns_gethostbyaddr2_r-check-and-adjust-the-buffer-alignment.patch | 35 35 0 0 +
/trunk/patches/glibc/2_9/250-resolv-dynamic.patch | 44 44 0 0 +
/trunk/patches/glibc/2_9/300-2.9-check_native-headers.patch | 22 22 0 0 +
/trunk/patches/glibc/2_9/310-2.3.6-fix-pr631.patch | 50 50 0 0 +
/trunk/patches/glibc/2_9/130-add_prio-macros.patch | 26 26 0 0 +
/trunk/patches/glibc/2_9/260-fadvise64_64.patch | 30 30 0 0 +
/trunk/patches/glibc/2_9/440-alpha-glibc-2.4-xstat.patch | 249 249 0 0 ++++++
/trunk/patches/glibc/2_9/170-2.10-dns-no-gethostbyname4.patch | 35 35 0 0 +
/trunk/patches/glibc/2_9/230-2.3.3-localedef-fix-trampoline.patch | 74 74 0 0 ++
/trunk/patches/glibc/2_9/360-2.8-nscd-one-fork.patch | 45 45 0 0 +
/trunk/patches/glibc/2_9/480-alpha-glibc-2.8-cache-shape.patch | 18 18 0 0 +
/trunk/patches/glibc/2_9/210-2.9-strlen-hack.patch | 109 109 0 0 +++
/trunk/patches/glibc/2_9/320-2.9-assume-pipe2.patch | 59 59 0 0 +
/trunk/patches/glibc/2_9/100-ssp-compat.patch | 193 193 0 0 +++++
/trunk/patches/glibc/2_9/110-respect-env-CPPFLAGS.patch | 30 30 0 0 +
/trunk/patches/glibc/2_9/220-manual-no-perl.patch | 29 29 0 0 +
/trunk/patches/glibc/2_9/390-2.3.3_pre20040117-pt_pax.patch | 35 35 0 0 +
/trunk/patches/glibc/2_9/460-alpha-glibc-2.5-no-asm-elf-header.patch | 38 38 0 0 +
/trunk/patches/glibc/2_9/400-tests-sandbox-libdl-paths.patch | 198 198 0 0 +++++
/trunk/patches/glibc/2_9/240-i386-LOAD_PIC_REG.patch | 23 23 0 0 +
/trunk/patches/glibc/2_9/200-awk-in-C-locale.patch | 23 23 0 0 +
/trunk/patches/glibc/2_9/430-2.7-cross-compile-nptl.patch | 57 57 0 0 +
/trunk/patches/glibc/2_9/380-2.3.6-dl_execstack-PaX-support.patch | 71 71 0 0 ++
/trunk/patches/glibc/2_9/490-ptr-mangling.patch | 114 114 0 0 +++
/trunk/patches/glibc/2_9/470-alpha-glibc-2.8-creat.patch | 19 19 0 0 +
41 files changed, 3094 insertions(+)

# Options related to paths and install

comment "Paths"

config LOCAL_TARBALLS_DIR

    string

    prompt "Local tarballs directory"

    default ""

    help

      If you have previously downloaded the tarballs, enter the PATH where

      you stored them here.

config SAVE_TARBALLS

    bool

    prompt "Save new tarballs"

    default n

    depends on LOCAL_TARBALLS_DIR != ""

    help

      If you say 'y' here, new downloaded tarballs will be saved in the

      directory you entered above.

config WORK_DIR

    string

    prompt "Working directory"

    default "${CT_TOP_DIR}/targets"

    help

      Set this to the directory where all build actions will be done.

      The default is "${CT_TOP_DIR}/targets", and leaving this option

      empty will also use the default.

      You should not need to change that, except in one very peculiar

      setup:

       - your crosstool-NG source directory is on the network

       - you configured crosstool-NG with --local

      This kind of setup is a pain, as any action involving source file

      access would have to go through the wire. In this case, you should

      set CT_WORK_DIR to point to a path local to your machine, to avoid

      any network overhead.

      Do *NOT* change it if you don't know better.

config PREFIX_DIR

    string

    prompt "Prefix directory"

    default "${HOME}/x-tools/${CT_TARGET}"

    help

      This is the path the toolchain will run from.

config INSTALL_DIR

    string

#    prompt "Install directory"

    default "${CT_PREFIX_DIR}"

#    help

#      This is the path the toolchain will be installed into.

#      

#      Normally, you would set this to ${CT_PREFIX_DIR}, but if for some reasons

#      you can't write there, you can install somewhere else and have a third

#      person do the install for you.

#      The reason you might also want to install elsewhere is if you are going

#      to package your shinny new toolchain for distribution.

config CUSTOM_PATCH

    bool

    prompt "Use custom patch directory"

    default n

    help

      If you have custom patches that you want to be applied, say 'Y' here and

      enter the path directory below.

      Note that you must ensure that the patch directory is arranged the same

      way the official directory is.

config CUSTOM_PATCH_ONLY

    bool

    prompt "Only use custom patches"

    default n

    depends on CUSTOM_PATCH

    help

      Don't apply patches coming with crosstool-NG, only those patches available

      in the directory below.

      If you say 'N' here, then the patches provided with crosstool-NG will be

      applied first, and then your patches.

config CUSTOM_PATCH_DIR

    string

    prompt "Custom patch directory"

    default ""

    depends on CUSTOM_PATCH

    help

      Enter the custom patch directory here.

config REMOVE_DOCS

    bool

    prompt "Remove documentation"

    default y

    help

      Remove the installed documentation (man and info pages).

      Gains around 8MiB for a uClibc-based, C and C++ compiler.

config INSTALL_DIR_RO

    bool

    prompt "Render the toolchain read-only"

    default y

    help

      Render the directory of the toolchain (and its sub-directories)

      read-only.

      Usefull for toolchains destined for production.