commit 1499aabd59592759e3143615ad981995ba0b36a4 (HEAD -> gentoo/2.29, tag: gentoo/glibc-2.29-5, gentoo/gentoo/2.29)
Author: Sergei Trofimovich <slyfox@gentoo.org>
Date:   Sun Sep 1 17:36:22 2019 +0100

    Revert "Gentoo: Fix 'make install-headers' when cross-compiler is not available yet."
    
    This reverts commit 6cbeeefee981729532160767e3dbbc6ff37295d9.
    
    In https://sourceware.org/PR24577 we discovered that riscv
    can't really install libc headers as it needs a cross-compiler.
    
    Bug: https://sourceware.org/PR24577
    Bug: https://bugs.gentoo.org/692052
    Bug: https://bugs.gentoo.org/686248

 Makerules | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

commit 3c7437b4cf77eea405413f70df21a446be1d14c6
Author: Andreas K. Huettel <dilfridge@gentoo.org>
Date:   Mon Aug 5 18:28:34 2019 +0200

    [no-patch] Gentoo: Add compile-locales warning functionality to locale-gen
    
    Backport from 2.30 branch
    
    Signed-off-by: Andreas K. Huettel <dilfridge@gentoo.org>

 scripts/gentoo/extra/locale/locale-gen | 11 +++++++++++
 1 file changed, 11 insertions(+)

commit 6cbeeefee981729532160767e3dbbc6ff37295d9 (tag: gentoo/glibc-2.29-4)
Author: Sergei Trofimovich <slyfox@gentoo.org>
Date:   Thu Jul 25 22:54:02 2019 +0100

    Gentoo: Fix 'make install-headers' when cross-compiler is not available yet.
    
    Gentoo passes CPPFLAGS='-D__riscv_xlen=64 ... ' to work it around.
    
    Unfortunately depend file generation does not use $(CPPFLAGS).
    This causes install to fail as:
    
    ../sysdeps/riscv/bits/wordsize.h:22:3: error: #error unsupported ABI
       22 | # error unsupported ABI
          |   ^~~~~
    ../sysdeps/riscv/bits/wordsize.h:28:3: error: #error "rv32i-based targets are not supported"
       28 | # error "rv32i-based targets are not supported"
          |   ^~~~~
    
    The fix is to pass through 'CPPFLAGS' (and 'CFLAGS' while at it).
    
    Bug: https://bugs.gentoo.org/686248
    Bug: https://sourceware.org/PR24577
    Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org>

 Makerules | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

commit 95d725c0ee37ced821e24b89b59788a91479fa63 (gentoo/gentoo/2.29-hygiene)
Author: Dmitry V. Levin <ldv@altlinux.org>
Date:   Wed Feb 13 01:20:51 2019 +0000

    libio: do not attempt to free wide buffers of legacy streams [BZ #24228]
    
    Commit a601b74d31ca086de38441d316a3dee24c866305 aka glibc-2.23~693
    ("In preparation for fixing BZ#16734, fix failure in misc/tst-error1-mem
    when _G_HAVE_MMAP is turned off.") introduced a regression:
    _IO_unbuffer_all now invokes _IO_wsetb to free wide buffers of all
    files, including legacy standard files which are small statically
    allocated objects that do not have wide buffers and the _mode member,
    causing memory corruption.
    
    Another memory corruption in _IO_unbuffer_all happens when -1
    is assigned to the _mode member of legacy standard files that
    do not have it.
    
    [BZ #24228]
    * libio/genops.c (_IO_unbuffer_all)
    [SHLIB_COMPAT (libc, GLIBC_2_0, GLIBC_2_1)]: Do not attempt to free wide
    buffers and access _IO_FILE_complete members of legacy libio streams.
    * libio/tst-bz24228.c: New file.
    * libio/tst-bz24228.map: Likewise.
    * libio/Makefile [build-shared] (tests): Add tst-bz24228.
    [build-shared] (generated): Add tst-bz24228.mtrace and
    tst-bz24228.check.
    [run-built-tests && build-shared] (tests-special): Add
    $(objpfx)tst-bz24228-mem.out.
    (LDFLAGS-tst-bz24228, tst-bz24228-ENV): New variables.
    ($(objpfx)tst-bz24228-mem.out): New rule.
    
    (cherry picked from commit 21cc130b78a4db9113fb6695e2b951e697662440)
    (cherry picked from commit 34fb5f61d3c3f4b8fc616ea259fa19168b58ecd4)
    Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org>

 ChangeLog             | 17 +++++++++++++++++
 NEWS                  |  1 +
 libio/Makefile        | 14 +++++++++++++-
 libio/genops.c        | 16 ++++++++++++----
 libio/tst-bz24228.c   | 29 +++++++++++++++++++++++++++++
 libio/tst-bz24228.map |  5 +++++
 6 files changed, 77 insertions(+), 5 deletions(-)

commit 92080495bf067753eaf967bffe53f60bfaaf6c98
Author: Zack Weinberg <zackw@panix.com>
Date:   Mon Mar 11 10:59:27 2019 -0400

    Use a proper C tokenizer to implement the obsolete typedefs test.
    
    The test for obsolete typedefs in installed headers was implemented
    using grep, and could therefore get false positives on e.g. “ulong”
    in a comment.  It was also scanning all of the headers included by
    our headers, and therefore testing headers we don’t control, e.g.
    Linux kernel headers.
    
    This patch splits the obsolete-typedef test from
    scripts/check-installed-headers.sh to a separate program,
    scripts/check-obsolete-constructs.py.  Being implemented in Python,
    it is feasible to make it tokenize C accurately enough to avoid false
    positives on the contents of comments and strings.  It also only
    examines $(headers) in each subdirectory--all the headers we install,
    but not any external dependencies of those headers.  Headers whose
    installed name starts with finclude/ are ignored, on the assumption
    that they contain Fortran.
    
    It is also feasible to make the new test understand the difference
    between _defining_ the obsolete typedefs and _using_ the obsolete
    typedefs, which means posix/{bits,sys}/types.h no longer need to be
    exempted.  This uncovered an actual bug in bits/types.h: __quad_t and
    __u_quad_t were being used to define __S64_TYPE, __U64_TYPE,
    __SQUAD_TYPE and __UQUAD_TYPE.  These are changed to __int64_t and
    __uint64_t respectively.  This is a safe change, despite the comments
    in bits/types.h claiming a difference between __quad_t and __int64_t,
    because those comments are incorrect.  In all current ABIs, both
    __quad_t and __int64_t are ‘long’ when ‘long’ is a 64-bit type, and
    ‘long long’ when ‘long’ is a 32-bit type, and similarly for __u_quad_t
    and __uint64_t.  (Changing the types to be what the comments say they
    are would be an ABI break, as it affects C++ name mangling.)  This
    patch includes a minimal change to make the comments not completely
    wrong.
    
    sys/types.h was defining the legacy BSD u_intN_t typedefs using a
    construct that was not necessarily consistent with how the C99 uintN_t
    typedefs are defined, and is also too complicated for the new script to
    understand (it lexes C relatively accurately, but it does not attempt
    to expand preprocessor macros, nor does it do any actual parsing).
    This patch cuts all of that out and uses bits/types.h's __uintN_t typedefs
    to define u_intN_t instead.  This is verified to not change the ABI on
    any supported architecture, via the c++-types test, which means u_intN_t
    and uintN_t were, in fact, consistent on all supported architectures.
    
    Reviewed-by: Carlos O'Donell <carlos@redhat.com>
    
            * scripts/check-obsolete-constructs.py: New test script.
            * scripts/check-installed-headers.sh: Remove tests for
            obsolete typedefs, superseded by check-obsolete-constructs.py.
            * Rules: Run scripts/check-obsolete-constructs.py over $(headers)
            as a special test.  Update commentary.
            * posix/bits/types.h (__SQUAD_TYPE, __S64_TYPE): Define as __int64_t.
            (__UQUAD_TYPE, __U64_TYPE): Define as __uint64_t.
            Update commentary.
            * posix/sys/types.h (__u_intN_t): Remove.
            (u_int8_t): Typedef using __uint8_t.
            (u_int16_t): Typedef using __uint16_t.
            (u_int32_t): Typedef using __uint32_t.
            (u_int64_t): Typedef using __uint64_t.
    
    (cherry picked from commit 711a322a235d4c8177713f11aa59156603b94aeb)
    (cherry picked from commit 2ec0b166bf04e22bb6921a08bb1a1131b57889a1)
    Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org>

 ChangeLog                            |  16 ++
 Rules                                |   5 +-
 posix/bits/types.h                   |  10 +-
 posix/sys/types.h                    |  33 +--
 scripts/check-installed-headers.sh   |  37 +--
 scripts/check-obsolete-constructs.py | 466 +++++++++++++++++++++++++++++++++++
 6 files changed, 504 insertions(+), 63 deletions(-)

commit 5d3a348b8845ad430ad0d2d8eae42f536c2fd146
Author: Florian Weimer <fweimer@redhat.com>
Date:   Wed Jun 5 14:02:05 2019 +0200

    malloc: Fix warnings in tests with GCC 9
    
    This is a partial backport of test changes in commit
    9bf8e29ca136094f73f69f725f15c51facc97206 ("malloc: make malloc fail
    with requests larger than PTRDIFF_MAX (BZ#23741)"), without the
    actual functionality changes.
    
    (cherry picked from commit bd0a325b6a263ae9dd9107d3476b1a594f20382a)
    Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org>

 ChangeLog                     |  7 +++++++
 malloc/tst-malloc-too-large.c | 39 +++++++++++++++++++++++++++++++++++++++
 malloc/tst-memalign.c         | 10 ++++++++++
 3 files changed, 56 insertions(+)

commit c0b36db27eb8f0cd901a8857f6ccf5ec5127cf0f
Author: Wilco Dijkstra <wdijkstr@arm.com>
Date:   Fri May 10 16:38:21 2019 +0100

    Fix tcache count maximum (BZ #24531)
    
    The tcache counts[] array is a char, which has a very small range and thus
    may overflow.  When setting tcache_count tunable, there is no overflow check.
    However the tunable must not be larger than the maximum value of the tcache
    counts[] array, otherwise it can overflow when filling the tcache.
    
            [BZ #24531]
            * malloc/malloc.c (MAX_TCACHE_COUNT): New define.
            (do_set_tcache_count): Only update if count is small enough.
            * manual/tunables.texi (glibc.malloc.tcache_count): Document max value.
    
    (cherry picked from commit 5ad533e8e65092be962e414e0417112c65d154fb)
    (cherry picked from commit 95d66fecaabbc92ab53027e808f0fc1929c9f21a)
    Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org>

 ChangeLog            | 7 +++++++
 malloc/malloc.c      | 9 +++++++--
 manual/tunables.texi | 4 ++--
 3 files changed, 16 insertions(+), 4 deletions(-)

commit ce808c48ff3451a990775f49f6fee992d883685a
Author: Mark Wielaard <mark@klomp.org>
Date:   Thu May 16 15:25:40 2019 +0200

    Update NEWS for BZ#24476 Guard __dlerror_main_freeres.
    
    (cherry picked from commit 980cb43f15c4320afc6272e7a508f1415413b945)
    Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org>

 NEWS | 1 +
 1 file changed, 1 insertion(+)

commit c59727b3f4dd168d47a69e2842e0126943e60288
Author: Mark Wielaard <mark@klomp.org>
Date:   Wed May 15 17:14:01 2019 +0200

    dlfcn: Guard __dlerror_main_freeres with __libc_once_get (once) [BZ#24476]
    
    dlerror.c (__dlerror_main_freeres) will try to free resources which only
    have been initialized when init () has been called. That function is
    called when resources are needed using __libc_once (once, init) where
    once is a __libc_once_define (static, once) in the dlerror.c file.
    Trying to free those resources if init () hasn't been called will
    produce errors under valgrind memcheck. So guard the freeing of those
    resources using __libc_once_get (once) and make sure we have a valid
    key. Also add a similar guard to __dlerror ().
    
            * dlfcn/dlerror.c (__dlerror_main_freeres): Guard using
            __libc_once_get (once) and static_bug == NULL.
            (__dlerror): Check we have a valid key, set result to static_buf
            otherwise.
    
    Reviewed-by: Carlos O'Donell <carlos@redhat.com>
    (cherry picked from commit 11b451c8868d8a2b0edc5dfd44fc58d9ee538be0)
    (cherry picked from commit e3f828b8bd6e21922da8be8dee35edef09382d8d)
    Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org>

 ChangeLog       |  8 ++++++++
 dlfcn/dlerror.c | 29 +++++++++++++++++++++--------
 2 files changed, 29 insertions(+), 8 deletions(-)

commit 07f27916f42ceaac959b26d60ff54a807fa2f21d
Author: Andreas Schwab <schwab@suse.de>
Date:   Wed May 15 17:09:05 2019 +0200

    Fix crash in _IO_wfile_sync (bug 20568)
    
    When computing the length of the converted part of the stdio buffer, use
    the number of consumed wide characters, not the (negative) distance to the
    end of the wide buffer.
    
    (cherry picked from commit 32ff397533715988c19cbf3675dcbd727ec13e18)
    (cherry picked from commit c6177be4b92d5d7df50a785652d1912db511423e)
    Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org>

 ChangeLog                  | 10 ++++++++++
 NEWS                       |  1 +
 libio/Makefile             |  3 ++-
 libio/tst-wfile-sync.c     | 39 +++++++++++++++++++++++++++++++++++++++
 libio/tst-wfile-sync.input |  1 +
 libio/wfileops.c           |  5 +++--
 6 files changed, 56 insertions(+), 3 deletions(-)

commit fba150eb133d2e91bd8f6ff64fb8e9af173d4306
Author: Adam Maris <amaris@redhat.com>
Date:   Thu Mar 14 16:51:16 2019 -0400

    malloc: Check for large bin list corruption when inserting unsorted chunk
    
    Fixes bug 24216. This patch adds security checks for bk and bk_nextsize pointers
    of chunks in large bin when inserting chunk from unsorted bin. It was possible
    to write the pointer to victim (newly inserted chunk) to arbitrary memory
    locations if bk or bk_nextsize pointers of the next large bin chunk
    got corrupted.
    
    (cherry picked from commit 5b06f538c5aee0389ed034f60d90a8884d6d54de)
    (cherry picked from commit 52b7cd6e9a701bb203023d56e84551943dc6a4c0)
    Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org>

 malloc/malloc.c | 4 ++++
 1 file changed, 4 insertions(+)

commit 978f0234e258d054fd332a95d567062f0f171da4
Author: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Date:   Fri Apr 26 13:58:31 2019 +0200

    elf: Fix pldd (BZ#18035)
    
    Since 9182aa67994 (Fix vDSO l_name for GDB's, BZ#387) the initial link_map
    for executable itself and loader will have both l_name and l_libname->name
    holding the same value due:
    
     elf/dl-object.c
    
     95   new->l_name = *realname ? realname : (char *) newname->name + libname_len - 1;
    
    Since newname->name points to new->l_libname->name.
    
    This leads to pldd to an infinite call at:
    
     elf/pldd-xx.c
    
    203     again:
    204       while (1)
    205         {
    206           ssize_t n = pread64 (memfd, tmpbuf.data, tmpbuf.length, name_offset);
    
    228           /* Try the l_libname element.  */
    229           struct E(libname_list) ln;
    230           if (pread64 (memfd, &ln, sizeof (ln), m.l_libname) == sizeof (ln))
    231             {
    232               name_offset = ln.name;
    233               goto again;
    234             }
    
    Since the value at ln.name (l_libname->name) will be the same as previously
    read. The straightforward fix is just avoid the check and read the new list
    entry.
    
    I checked also against binaries issues with old loaders with fix for BZ#387,
    and pldd could dump the shared objects.
    
    Checked on x86_64-linux-gnu, i686-linux-gnu, aarch64-linux-gnu, and
    powerpc64le-linux-gnu.
    
            [BZ #18035]
            * elf/Makefile (tests-container): Add tst-pldd.
            * elf/pldd-xx.c: Use _Static_assert in of pldd_assert.
            (E(find_maps)): Avoid use alloca, use default read file operations
            instead of explicit LFS names, and fix infinite loop.
            * elf/pldd.c: Explicit set _FILE_OFFSET_BITS, cleanup headers.
            (get_process_info): Use _Static_assert instead of assert, use default
            directory operations instead of explicit LFS names, and free some
            leadek pointers.
            * elf/tst-pldd.c: New file.
    
    (cherry picked from commit 1a4c27355e146b6d8cc6487b998462c7fdd1048f)
    (cherry picked from commit eaea1dfbe95a31c29adc259100569962cddb6f19)
    Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org>

 ChangeLog      |  13 +++++++
 NEWS           |   1 +
 elf/Makefile   |   1 +
 elf/pldd-xx.c  | 114 +++++++++++++++++++------------------------------------
 elf/pldd.c     |  64 +++++++++++++++----------------
 elf/tst-pldd.c | 118 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 6 files changed, 203 insertions(+), 108 deletions(-)

commit f8a90b854e463eeb0b7462b5ce90aea5af4f469d
Author: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Date:   Fri Apr 12 17:39:53 2019 -0300

    support: Add support_capture_subprogram
    
    Its API is similar to support_capture_subprocess, but rather creates a
    new process based on the input path and arguments.  Under the hoods it
    uses posix_spawn to create the new process.
    
    It also allows the use of other support_capture_* functions to check
    for expected results and free the resources.
    
    Checked on x86_64-linux-gnu.
    
            * support/Makefile (libsupport-routines): Add support_subprocess,
            xposix_spawn, xposix_spawn_file_actions_addclose, and
            xposix_spawn_file_actions_adddup2.
            (tst-support_capture_subprocess-ARGS): New rule.
            * support/capture_subprocess.h (support_capture_subprogram): New
            prototype.
            * support/support_capture_subprocess.c (support_capture_subprocess):
            Refactor to use support_subprocess and support_capture_poll.
            (support_capture_subprogram): New function.
            * support/tst-support_capture_subprocess.c (write_mode_to_str,
            str_to_write_mode, test_common, parse_int, handle_restart,
            do_subprocess, do_subprogram, do_multiple_tests): New functions.
            (do_test): Add support_capture_subprogram tests.
            * support/subprocess.h: New file.
            * support/support_subprocess.c: Likewise.
            * support/xposix_spawn.c: Likewise.
            * support/xposix_spawn_file_actions_addclose.c: Likewise.
            * support/xposix_spawn_file_actions_adddup2.c: Likewise.
            * support/xspawn.h: Likewise.
    
    Reviewed-by: Carlos O'Donell <carlos@redhat.com>
    (cherry picked from commit 0e169691290a6d2187a4ff41495fc5678cbfdcdc)
    (cherry picked from commit f62d21a1f0107e6f7182f346293583c9121a877d)
    Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org>

 ChangeLog                                    |  22 ++++
 support/Makefile                             |   6 +
 support/capture_subprocess.h                 |   6 +
 support/subprocess.h                         |  49 +++++++
 support/support_capture_subprocess.c         |  80 ++++++------
 support/support_subprocess.c                 | 152 ++++++++++++++++++++++
 support/tst-support_capture_subprocess.c     | 183 +++++++++++++++++++++++++--
 support/xposix_spawn.c                       |  32 +++++
 support/xposix_spawn_file_actions_addclose.c |  29 +++++
 support/xposix_spawn_file_actions_adddup2.c  |  30 +++++
 support/xspawn.h                             |  34 +++++
 11 files changed, 573 insertions(+), 50 deletions(-)

commit 4753b66c8993d47a918993d62379c749a1aa28a9
Author: Florian Weimer <fweimer@redhat.com>
Date:   Thu Apr 25 14:58:13 2019 +0200

    Revert "memusagestat: use local glibc when linking [BZ #18465]"
    
    This reverts commit 42dfc13abf6fbb4c7a0215238eb636b7d374e0e0.
    
    The position of the -Wl,-rpath-link= options on the linker command
    line is not correct, so the new way of linking memusagestat does not
    always work.
    
    (cherry picked from commit 0744a268bc73e42b14b83e4cf3d083c6df6344e8)
    Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org>

 ChangeLog       | 7 -------
 NEWS            | 1 -
 malloc/Makefile | 4 ++--
 3 files changed, 2 insertions(+), 10 deletions(-)

commit 5946442448e2448089aa92b19b97b3c69eb52547
Author: Mike Frysinger <vapier@gentoo.org>
Date:   Wed Apr 24 19:07:46 2019 +0200

    memusagestat: use local glibc when linking [BZ #18465]
    
    The memusagestat is the only binary that has its own link line which
    causes it to be linked against the existing installed C library.  It
    has been this way since it was originally committed in 1999, but I
    don't see any reason as to why.  Since we want all the programs we
    build locally to be against the new copy of glibc, change the build
    to be like all other programs.
    
    (cherry picked from commit f9b645b4b0a10c43753296ce3fa40053fa44606a)
    (cherry picked from commit 42dfc13abf6fbb4c7a0215238eb636b7d374e0e0)
    Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org>

 ChangeLog       | 7 +++++++
 NEWS            | 1 +
 malloc/Makefile | 4 ++--
 3 files changed, 10 insertions(+), 2 deletions(-)

commit 1dad440a824f28a6f69e1b56b86f75855a0a8923
Author: Carlos O'Donell <carlos@redhat.com>
Date:   Mon Apr 15 20:49:32 2019 +0200

    malloc: Set and reset all hooks for tracing (Bug 16573)
    
    If an error occurs during the tracing operation, particularly during a
    call to lock_and_info() which calls _dl_addr, we may end up calling back
    into the malloc-subsystem and relock the loader lock and deadlock. For
    all intents and purposes the call to _dl_addr can call any of the malloc
    family API functions and so we should disable all tracing before calling
    such loader functions.  This is similar to the strategy that the new
    malloc tracer takes when calling the real malloc, namely that all
    tracing ceases at the boundary to the real function and any faults at
    that point are the purvue of the library (though the new tracer does
    this on a per-thread basis in an MT-safe fashion). Since the new tracer
    and the hook deprecation are not yet complete we must fix these issues
    where we can.
    
    Tested on x86_64 with no regressions.
    
    Co-authored-by: Kwok Cheung Yeung <kcy@codesourcery.com>
    Reviewed-by: DJ Delorie <dj@redhat.com>
    (cherry picked from commit e621246ec6393ea08ae50310f9d5e72500f8c9bc)
    (cherry picked from commit dcd2b97dd1d695445d45beb4daa815cfe06691dd)
    Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org>

 ChangeLog       | 15 ++++++++++++
 NEWS            |  1 +
 malloc/mtrace.c | 72 ++++++++++++++++++++++++++++++++++++---------------------
 3 files changed, 62 insertions(+), 26 deletions(-)

commit e2b2a485d3aea7ae0a183c25f1bc0a7b8f9f43c3 (tag: gentoo/glibc-2.29-3)
Author: TAMUKI Shoichi <tamuki@linet.gr.jp>
Date:   Tue Apr 2 16:46:55 2019 +0900

    ja_JP locale: Add entry for the new Japanese era [BZ #22964]
    
    The Japanese era name will be changed on May 1, 2019.  The Japanese
    government made a preliminary announcement on April 1, 2019.
    
    The glibc ja_JP locale must be updated to include the new era name for
    strftime's alternative year format support.
    
    This is a minimal cherry pick of just the required locale changes.
    
    (cherry picked from commit 466afec30896585b60c2106df7a722a86247c9f3)
    (cherry picked from commit 0941350c20a52447e53c5169354408e3db591f73)
    Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org>

 ChangeLog                | 6 ++++++
 NEWS                     | 4 ++++
 localedata/locales/ja_JP | 4 +++-
 3 files changed, 13 insertions(+), 1 deletion(-)

commit e8e11b6d5b679a6034ff121eee3153fc89ba49da (tag: gentoo/glibc-2.29-2)
Author: TAMUKI Shoichi <tamuki@linet.gr.jp>
Date:   Sat Mar 2 21:00:28 2019 +0900

    ja_JP: Change the offset for Taisho gan-nen from 2 to 1 [BZ #24162]
    
    The offset in era-string format for Taisho gan-nen (1912) is currently
    defined as 2, but it should be 1.  So fix it.  "Gan-nen" means the 1st
    (origin) year, Taisho started on July 30, 1912.
    
    Reported-by: Morimitsu, Junji <junji.morimitsu@hpe.com>
    Reviewed-by: Rafal Luzynski <digitalfreak@lingonborough.com>
    
    ChangeLog:
    
            [BZ #24162]
            * localedata/locales/ja_JP (LC_TIME): Change the offset for Taisho
            gan-nen from 2 to 1.  Problem reported by Morimitsu, Junji.
    
    (cherry picked from commit 31effacee2fc1b327bedc9a5fcb4b83f227c6539)
    (cherry picked from commit e28ad442e73b00ae2047d89c8cc7f9b2a0de5436)
    Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org>

 ChangeLog                | 6 ++++++
 localedata/locales/ja_JP | 2 +-
 2 files changed, 7 insertions(+), 1 deletion(-)

commit 21eb87321ff817fee0e40d04851a493cefb8db5f
Author: Stefan Liebler <stli@linux.ibm.com>
Date:   Thu Mar 21 09:14:26 2019 +0100

    S390: Mark vx and vxe as important hwcap.
    
    This patch adds vx and vxe as important hwcaps
    which allows one to provide shared libraries
    tuned for platforms with non-vx/-vxe, vx or vxe.
    
    ChangeLog:
    
            * sysdeps/s390/dl-procinfo.h (HWCAP_IMPORTANT):
            Add HWCAP_S390_VX and HWCAP_S390_VXE.
    
    (cherry picked from commit 61f5e9470fb397a4c334938ac5a667427d9047df)
    
    Conflicts:
            ChangeLog
    (cherry picked from commit 6eb48fe80cb6dd3ef536e86d005976d1c22b170e)
    Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org>

 ChangeLog                  | 5 +++++
 sysdeps/s390/dl-procinfo.h | 3 ++-
 2 files changed, 7 insertions(+), 1 deletion(-)

commit bfb5bad9444c00874e7d54a9c1735374cb94288b
Author: Aurelien Jarno <aurelien@aurel32.net>
Date:   Sat Mar 16 22:59:56 2019 +0100

    Record CVE-2019-9169 in NEWS and ChangeLog [BZ #24114]
    
    (cherry picked from commit b626c5aa5d0673a9caa48fb79fba8bda237e6fa8)
    (cherry picked from commit 10dd17da710fd32aaf1f2187544d80064b8c4ee0)
    Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org>

 ChangeLog | 1 +
 NEWS      | 4 ++++
 2 files changed, 5 insertions(+)

commit f7b4a9cb915c6142b1f56062772b49ba7ff13618
Author: Paul Eggert <eggert@cs.ucla.edu>
Date:   Mon Jan 21 11:08:13 2019 -0800

    regex: fix read overrun [BZ #24114]
    
    Problem found by AddressSanitizer, reported by Hongxu Chen in:
    https://debbugs.gnu.org/34140
    * posix/regexec.c (proceed_next_node):
    Do not read past end of input buffer.
    
    (cherry picked from commit 583dd860d5b833037175247230a328f0050dbfe9)
    (cherry picked from commit 4d0b1b0f61bfba034e9e76a1d76acc59c975238f)
    Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org>

 ChangeLog       | 8 ++++++++
 posix/regexec.c | 6 ++++--
 2 files changed, 12 insertions(+), 2 deletions(-)

commit 145bc67a6683fc60dd9e71e6cfa87a5906fd8bc1
Author: Stefan Liebler <stli@linux.ibm.com>
Date:   Wed Mar 13 10:45:35 2019 +0100

    Fix output of LD_SHOW_AUXV=1.
    
    Starting with commit 1616d034b61622836d3a36af53dcfca7624c844e
    the output was corrupted on some platforms as _dl_procinfo
    was called for every auxv entry and on some architectures like s390
    all entries were represented as "AT_HWCAP".
    
    This patch is removing the condition and let _dl_procinfo decide if
    an entry is printed in a platform specific or generic way.
    This patch also adjusts all _dl_procinfo implementations which assumed
    that they are only called for AT_HWCAP or AT_HWCAP2. They are now just
    returning a non-zero-value for entries which are not handled platform
    specifc.
    
    ChangeLog:
    
            * elf/dl-sysdep.c (_dl_show_auxv): Remove condition and always
            call _dl_procinfo.
            * sysdeps/unix/sysv/linux/s390/dl-procinfo.h (_dl_procinfo):
            Ignore types other than AT_HWCAP.
            * sysdeps/sparc/dl-procinfo.h (_dl_procinfo): Likewise.
            * sysdeps/unix/sysv/linux/i386/dl-procinfo.h (_dl_procinfo):
            Likewise.
            * sysdeps/powerpc/dl-procinfo.h (_dl_procinfo): Adjust comment
            in the case of falling back to generic output mechanism.
            * sysdeps/unix/sysv/linux/arm/dl-procinfo.h (_dl_procinfo):
            Likewise.
    
    (cherry picked from commit 7c6513082b787a7d36ab7d75720b48f8a216089c)
    
    Conflicts:
            ChangeLog
    (cherry picked from commit bc6f839fb4066be83272c735e662850af2595777)
    Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org>

 ChangeLog                                  | 14 ++++++++++++++
 elf/dl-sysdep.c                            | 11 +++--------
 sysdeps/powerpc/dl-procinfo.h              |  2 +-
 sysdeps/sparc/dl-procinfo.h                |  4 ++--
 sysdeps/unix/sysv/linux/arm/dl-procinfo.h  |  2 +-
 sysdeps/unix/sysv/linux/i386/dl-procinfo.h |  4 ++--
 sysdeps/unix/sysv/linux/s390/dl-procinfo.h |  4 ++--
 7 files changed, 25 insertions(+), 16 deletions(-)

commit c06c02f45b5d13644ef0fb02ea7adee5f2be5955
Author: Florian Weimer <fweimer@redhat.com>
Date:   Fri Feb 15 21:27:01 2019 +0100

    nptl: Fix invalid Systemtap probe in pthread_join [BZ #24211]
    
    After commit f1ac7455831546e5dca0ed98fe8af2686fae7ce6 ("arm: Use "nr"
    constraint for Systemtap probes [BZ #24164]"), we load pd->result into
    a register in the probe below:
    
          /* Free the TCB.  */
          __free_tcb (pd);
        }
      else
        pd->joinid = NULL;
    
      LIBC_PROBE (pthread_join_ret, 3, threadid, result, pd->result);
    
    However, at this point, the thread descriptor has been freed.  If the
    thread stack does not fit into the thread stack cache, the memory will
    have been unmapped, and the program will crash in the probe.
    
    (cherry picked from commit bc10e22c90e42613bd5dafb77b80a9ea1759dd1b)
    (cherry picked from commit 067fc32968b601493f4b247a3ac00caeea3f3d61)
    Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org>

 ChangeLog                  | 6 ++++++
 NEWS                       | 1 +
 nptl/pthread_join_common.c | 5 +++--
 3 files changed, 10 insertions(+), 2 deletions(-)

commit 5eb7abb59f3f021edbaabc2305697d818e0421de
Author: Florian Weimer <fweimer@redhat.com>
Date:   Fri Feb 8 12:54:41 2019 +0100

    nptl: Avoid fork handler lock for async-signal-safe fork [BZ #24161]
    
    Commit 27761a1042daf01987e7d79636d0c41511c6df3c ("Refactor atfork
    handlers") introduced a lock, atfork_lock, around fork handler list
    accesses.  It turns out that this lock occasionally results in
    self-deadlocks in malloc/tst-mallocfork2:
    
    (gdb) bt
    #0  __lll_lock_wait_private ()
        at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:63
    #1  0x00007f160c6f927a in __run_fork_handlers (who=(unknown: 209394016),
        who@entry=atfork_run_prepare) at register-atfork.c:116
    #2  0x00007f160c6b7897 in __libc_fork () at ../sysdeps/nptl/fork.c:58
    #3  0x00000000004027d6 in sigusr1_handler (signo=<optimized out>)
        at tst-mallocfork2.c:80
    #4  sigusr1_handler (signo=<optimized out>) at tst-mallocfork2.c:64
    #5  <signal handler called>
    #6  0x00007f160c6f92e4 in __run_fork_handlers (who=who@entry=atfork_run_parent)
        at register-atfork.c:136
    #7  0x00007f160c6b79a2 in __libc_fork () at ../sysdeps/nptl/fork.c:152
    #8  0x0000000000402567 in do_test () at tst-mallocfork2.c:156
    #9  0x0000000000402dd2 in support_test_main (argc=1, argv=0x7ffc81ef1ab0,
        config=config@entry=0x7ffc81ef1970) at support_test_main.c:350
    #10 0x0000000000402362 in main (argc=<optimized out>, argv=<optimized out>)
        at ../support/test-driver.c:168
    
    If no locking happens in the single-threaded case (where fork is
    expected to be async-signal-safe), this deadlock is avoided.
    (pthread_atfork is not required to be async-signal-safe, so a fork
    call from a signal handler interrupting pthread_atfork is not
    a problem.)
    
    (cherry picked from commit 669ff911e2571f74a2668493e326ac9a505776bd)
    (cherry picked from commit c096b008d2671028c21ac8cf01f18a2083e73c44)
    Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org>

 ChangeLog              | 10 ++++++++++
 NEWS                   |  1 +
 nptl/register-atfork.c |  8 +++++---
 sysdeps/nptl/fork.c    |  6 +++---
 sysdeps/nptl/fork.h    |  8 +++++---
 5 files changed, 24 insertions(+), 9 deletions(-)

commit ac58012f6741295e0540b208d12bc1a3ea3a2620
Author: Stefan Liebler <stli@linux.ibm.com>
Date:   Thu Feb 7 15:18:36 2019 +0100

    Add compiler barriers around modifications of the robust mutex list for pthread_mutex_trylock. [BZ #24180]
    
    While debugging a kernel warning, Thomas Gleixner, Sebastian Sewior and
    Heiko Carstens found a bug in pthread_mutex_trylock due to misordered
    instructions:
    140:   a5 1b 00 01             oill    %r1,1
    144:   e5 48 a0 f0 00 00       mvghi   240(%r10),0   <--- THREAD_SETMEM (THREAD_SELF, robust_head.list_op_pending, NULL);
    14a:   e3 10 a0 e0 00 24       stg     %r1,224(%r10) <--- last THREAD_SETMEM of ENQUEUE_MUTEX_PI
    
    vs (with compiler barriers):
    140:   a5 1b 00 01             oill    %r1,1
    144:   e3 10 a0 e0 00 24       stg     %r1,224(%r10)
    14a:   e5 48 a0 f0 00 00       mvghi   240(%r10),0
    
    Please have a look at the discussion:
    "Re: WARN_ON_ONCE(!new_owner) within wake_futex_pi() triggerede"
    (https://lore.kernel.org/lkml/20190202112006.GB3381@osiris/)
    
    This patch is introducing the same compiler barriers and comments
    for pthread_mutex_trylock as introduced for pthread_mutex_lock and
    pthread_mutex_timedlock by commit 8f9450a0b7a9e78267e8ae1ab1000ebca08e473e
    "Add compiler barriers around modifications of the robust mutex list."
    
    ChangeLog:
    
            [BZ #24180]
            * nptl/pthread_mutex_trylock.c (__pthread_mutex_trylock):
            Add compiler barriers and comments.
    
    (cherry picked from commit 823624bdc47f1f80109c9c52dee7939b9386d708)
    (cherry picked from commit 44113a8ba24af23d7bbb174f9087a6b83a76289a)
    Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org>

 ChangeLog                    |  6 +++++
 nptl/pthread_mutex_trylock.c | 57 ++++++++++++++++++++++++++++++++++++++++----
 2 files changed, 59 insertions(+), 4 deletions(-)

commit 589c19d01ac764d8924e4778256e29a71537ade2
Author: Florian Weimer <fweimer@redhat.com>
Date:   Tue Feb 5 13:49:02 2019 +0100

    arm: Use "nr" constraint for Systemtap probes [BZ #24164]
    
    With the default "nor" constraint, current GCC will use the "o"
    constraint for constants, after emitting the constant to memory.  That
    results in unparseable Systemtap probe notes such as "-4@.L1052".
    Removing the "o" alternative and using "nr" instead avoids this.
    
    (cherry picked from commit f1ac7455831546e5dca0ed98fe8af2686fae7ce6)
    (cherry picked from commit 2de15ac95713a238dc258eb8977ecdfca811fc19)
    Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org>

 ChangeLog                            | 11 +++++++++++
 NEWS                                 |  1 +
 include/stap-probe.h                 |  1 +
 sysdeps/arm/stap-probe-machine.h     | 22 ++++++++++++++++++++++
 sysdeps/generic/stap-probe-machine.h | 19 +++++++++++++++++++
 5 files changed, 54 insertions(+)

commit d920143e58e46055388c3c1b338f85aea5b0ccba
Author: H.J. Lu <hjl.tools@gmail.com>
Date:   Mon Feb 4 08:55:52 2019 -0800

    x86-64 memcmp: Use unsigned Jcc instructions on size [BZ #24155]
    
    Since the size argument is unsigned. we should use unsigned Jcc
    instructions, instead of signed, to check size.
    
    Tested on x86-64 and x32, with and without --disable-multi-arch.
    
            [BZ #24155]
            CVE-2019-7309
            * NEWS: Updated for CVE-2019-7309.
            * sysdeps/x86_64/memcmp.S: Use RDX_LP for size.  Clear the
            upper 32 bits of RDX register for x32.  Use unsigned Jcc
            instructions, instead of signed.
            * sysdeps/x86_64/x32/Makefile (tests): Add tst-size_t-memcmp-2.
            * sysdeps/x86_64/x32/tst-size_t-memcmp-2.c: New test.
    
    (cherry picked from commit 3f635fb43389b54f682fc9ed2acc0b2aaf4a923d)
    (cherry picked from commit 726a78867b3144e9b9da10197bcf59bde3d8b2a4)
    Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org>

 ChangeLog                                | 11 +++++
 NEWS                                     | 17 +++++++
 sysdeps/x86_64/memcmp.S                  | 20 ++++----
 sysdeps/x86_64/x32/Makefile              |  3 +-
 sysdeps/x86_64/x32/tst-size_t-memcmp-2.c | 79 ++++++++++++++++++++++++++++++++
 5 files changed, 121 insertions(+), 9 deletions(-)

commit da5cb4c1cfa526faf5edfa129b73bde7ef3f6785
Author: Carlos O'Donell <carlos@redhat.com>
Date:   Mon Jan 21 22:50:12 2019 -0500

    nptl: Fix pthread_rwlock_try*lock stalls (Bug 23844)
    
    For a full analysis of both the pthread_rwlock_tryrdlock() stall
    and the pthread_rwlock_trywrlock() stall see:
    https://sourceware.org/bugzilla/show_bug.cgi?id=23844#c14
    
    In the pthread_rwlock_trydlock() function we fail to inspect for
    PTHREAD_RWLOCK_FUTEX_USED in __wrphase_futex and wake the waiting
    readers.
    
    In the pthread_rwlock_trywrlock() function we write 1 to
    __wrphase_futex and loose the setting of the PTHREAD_RWLOCK_FUTEX_USED
    bit, again failing to wake waiting readers during unlock.
    
    The fix in the case of pthread_rwlock_trydlock() is to check for
    PTHREAD_RWLOCK_FUTEX_USED and wake the readers.
    
    The fix in the case of pthread_rwlock_trywrlock() is to only write
    1 to __wrphase_futex if we installed the write phase, since all other
    readers would be spinning waiting for this step.
    
    We add two new tests, one exercises the stall for
    pthread_rwlock_trywrlock() which is easy to exercise, and one exercises
    the stall for pthread_rwlock_trydlock() which is harder to exercise.
    
    The pthread_rwlock_trywrlock() test fails consistently without the fix,
    and passes after. The pthread_rwlock_tryrdlock() test fails roughly
    5-10% of the time without the fix, and passes all the time after.
    
    Signed-off-by: Carlos O'Donell <carlos@redhat.com>
    Signed-off-by: Torvald Riegel <triegel@redhat.com>
    Signed-off-by: Rik Prohaska <prohaska7@gmail.com>
    Co-authored-by: Torvald Riegel <triegel@redhat.com>
    Co-authored-by: Rik Prohaska <prohaska7@gmail.com>
    (cherry picked from commit 5fc9ed4c4058bfbdf51ad6e7aac7d209b580e8c4)
    (cherry picked from commit 86013ef5cea322b8f4b9c22f230c22cce369e947)
    Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org>

 ChangeLog                         |  17 ++
 nptl/Makefile                     |   3 +-
 nptl/pthread_rwlock_tryrdlock.c   |  25 ++-
 nptl/pthread_rwlock_trywrlock.c   |   9 +-
 nptl/tst-rwlock-tryrdlock-stall.c | 355 ++++++++++++++++++++++++++++++++++++++
 nptl/tst-rwlock-trywrlock-stall.c | 108 ++++++++++++
 support/Makefile                  |   1 +
 support/xpthread_rwlock_destroy.c |  26 +++
 support/xthread.h                 |   1 +
 9 files changed, 534 insertions(+), 11 deletions(-)

commit 980c67b2fbfdcff372c5e92a04d962ce50f6f77d
Author: Andreas K. Hüttel <dilfridge@gentoo.org>
Date:   Sun Mar 24 17:00:05 2019 +0100

    Gentoo: Adapt nss/tst-nss-files-alias-leak to Gentoo aliases file location
    
    Bug: https://bugs.gentoo.org/680230
    Bug: https://bugs.gentoo.org/496510
    Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org>
    (cherry picked from commit 9f261121abac849dcdc923d4d391b5ec83ca2652)

 nss/tst-nss-files-alias-leak.c | 20 ++++++++++----------
 support/support_chroot.c       |  6 ++++++
 2 files changed, 16 insertions(+), 10 deletions(-)

commit c4412cc553e004fc6f20dd8e40ee47b38019635e (tag: gentoo/glibc-2.29-1)
Author: Andreas K. Hüttel <dilfridge@gentoo.org>
Date:   Fri Dec 14 20:43:04 2018 +0100

    Gentoo: force -O0 in conform tests to survive $CC changes
    
    In bug #659030 Gentoo started passing user's CFLAGS via $CC variable.
    conform tests should but are not ready to handle -O1/-O2 yet.
    Tests fail to validate headers due to inlining of weak symbol aliases
    and other problems. Let's force it back to -O0 until it's fixed upstream.
    
    Original patch by Sergei, ported to the new python test framework by Andreas
    
    Bug: https://bugs.gentoo.org/659030
    Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org>
    Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org>

 conform/conformtest.py   | 6 ++++--
 conform/linknamespace.py | 4 +++-
 2 files changed, 7 insertions(+), 3 deletions(-)

commit fb38e1b6aa4e822ffd83c038f7e47cbadd33e7f5
Author: Mike FABIAN <mfabian@redhat.com>
Date:   Mon Aug 10 15:58:12 2015 +0200

    Gentoo: Add a C.UTF-8 locale
    
    Source:
    https://src.fedoraproject.org/rpms/glibc/raw/master/f/glibc-c-utf8-locale.patch
    
    Notes from there:
    This patch needs to upstream as part of Carlos O'Donell
    <carlos@redhat.com>'s work on enabling upstream C.UTF-8 support. This
    work is currently blocked on cleaning up the test results to prove that
    full code-point sorting is working as intended.
    Note that this patch does not provide full code-point sorting as
    expected.
    This patch needs to upstream as soon as possible since it would be nice
    to have this in F29 and fixed.
    
    Further information:
    https://bugzilla.redhat.com/show_bug.cgi?id=902094
    https://sourceware.org/bugzilla/show_bug.cgi?id=17318
    https://bugs.gentoo.org/671024

 localedata/SUPPORTED |   1 +
 localedata/locales/C | 238 +++++++++++++++++++++++++++++++++++++++++++++++++++
 2 files changed, 239 insertions(+)

commit ea4625ce541fa1fed3ac9e7b6448dacfc0c08b09
Author: Andreas K. Hüttel <dilfridge@gentoo.org>
Date:   Mon Oct 22 22:34:13 2018 +0200

    Gentoo: Adapt to Gentoo-specific /etc/mail/aliases
    
    Patch by pacho2
    
    Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org>
    (cherry picked from commit 4e616cda056f471b799beba2b1cedc787ad4ecc0)

 nss/nss_files/files-alias.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

commit 2bedbd7548ed0157087f6ad6bdc3c58520fa840b
Author: Andreas K. Hüttel <dilfridge@gentoo.org>
Date:   Wed Jan 17 01:02:19 2018 +0100

    Gentoo: Disable test that fails because of the gethostbyname4_r revert

 nss/Makefile | 1 -
 1 file changed, 1 deletion(-)

commit 7e50a763572e5acc85e5ef5a52467e8e38b966b2
Author: Andreas K. Hüttel <dilfridge@gentoo.org>
Date:   Mon Sep 11 13:14:46 2017 +0200

    Gentoo: disable tests that fail only in sandbox

 elf/Makefile                     | 16 +---------------
 io/Makefile                      |  2 +-
 nptl/Makefile                    |  8 ++++----
 posix/Makefile                   |  4 ++--
 resolv/Makefile                  |  5 -----
 sysdeps/unix/sysv/linux/Makefile |  2 +-
 6 files changed, 9 insertions(+), 28 deletions(-)

commit e2b0987f740d9f3c2e64065f0259013f18e6881f
Author: Andreas K. Hüttel <dilfridge@gentoo.org>
Date:   Tue Aug 29 22:58:50 2017 +0200

    Revert "        * sysdeps/posix/getaddrinfo.c (gaih_inet): Only use gethostbyname4_r"
    
    This reverts commit 8479f23aa1d5e5477a37f46823856bdafaedfa46.
    
    See for the background
      https://sourceware.org/bugzilla/show_bug.cgi?id=16826
      https://bugs.gentoo.org/show_bug.cgi?id=600632
    
    This makes test resolv/tst-res_use_inet6 fail. Disable it.
    (cherry picked from commit 06a2a073a2c6fb3e1489af96e125daca248d0a03)

 resolv/Makefile             | 1 -
 sysdeps/posix/getaddrinfo.c | 9 ++-------
 2 files changed, 2 insertions(+), 8 deletions(-)

commit ee7204b2e396a7a1409e5b1722402fe54f6c30ff
Author: Andreas K. Hüttel <dilfridge@gentoo.org>
Date:   Wed Aug 23 13:26:49 2017 +0200

    [no-patch] Gentoo: Add support files
    
    * Source: https://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo/src/patchsets/glibc/extra/
    * The make-tarball script has been completely rewritten to work with git.
    * The c-stubs addon has been dropped since the addon mechanism is gone.
    * Updates to the nscd init script, see Gentoo bug 492814
    * Make patchset generation script also work with master
    * locale-gen: suppress ignored error when emptying already empty directory, bug 647188

 scripts/gentoo/README.Gentoo.patches     |  26 ++
 scripts/gentoo/extra/README              |   5 +
 scripts/gentoo/extra/etc/host.conf       |  24 ++
 scripts/gentoo/extra/etc/nscd            |  85 ++++++
 scripts/gentoo/extra/locale/locale-gen   | 433 +++++++++++++++++++++++++++++++
 scripts/gentoo/extra/locale/locale-gen.8 |  69 +++++
 scripts/gentoo/extra/locale/locale.gen   |  36 +++
 scripts/gentoo/extra/locale/locale.gen.5 |  77 ++++++
 scripts/gentoo/make-tarball.sh           | 107 ++++++++
 9 files changed, 862 insertions(+)

commit 179bcc56e9a90f2da8439dc2c6b09381794c52db
Author: Stephanie J. Lockwood-Childs <wormo@gentoo.org>
Date:   Tue Mar 13 01:57:21 2007 -0400

    Gentoo: support running tests under sandbox
    
    when glibc runs its tests, it does so by invoking the local library loader.
    in Gentoo, we build/run inside of our "sandbox" which itself is linked against
    libdl (so that it can load libraries and pull out symbols).  the trouble
    is that when you upgrade from an older glibc to the new one, often times
    internal symbols change name or abi.  this is normally OK as you cannot use
    libc.so from say version 2.3.6 but libpthread.so from say version 2.5, so
    we always say "keep all of the glibc libraries from the same build".  but
    when glibc runs its tests, it uses dynamic paths to point to its new local
    copies of libraries.  if the test doesnt use libdl, then glibc doesnt add
    its path, and when sandbox triggers the loading of libdl, glibc does so
    from the host system system.  this gets us into the case of all libraries
    are from the locally compiled version of glibc except for libdl.so.
    
    http://bugs.gentoo.org/56898

 Makeconfig                  | 2 +-
 iconvdata/run-iconv-test.sh | 2 +-
 nptl/tst-tls6.sh            | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

commit 55b00fe1c19ab0f4a27bdc9f0fa5d250d138b1fa
Author: Mike Frysinger <vapier@gentoo.org>
Date:   Wed Apr 1 02:15:48 2009 -0400

    Gentoo: disable ldconfig during install
    
    Do not bother running ldconfig on DESTDIR.  It's a waste of time as we
    won't use the result (portage will rebuild the cache after install).
    Also, the Gentoo sandbox does not currently catch chroot() behavior so
    we end up (incorrectly) flagging it as a violation as a write to /etc.
    
    http://sourceware.org/ml/libc-alpha/2012-08/msg00118.html
    https://bugs.gentoo.org/431038

 Makefile | 1 +
 1 file changed, 1 insertion(+)
