This is the mail archive of the
mailing list for the glibc project.
Re: v2: The GNU C Library 2.16 release plan
- From: Jeff Law <law at redhat dot com>
- To: Allan McRae <allan at archlinux dot org>
- Cc: "Carlos O'Donell" <carlos_odonell at mentor dot com>, libc-alpha <libc-alpha at sourceware dot org>, Andreas Jaegar <aj at suse dot com>, Paul Eggert <eggert at cs dot ucla dot edu>, "Ryan S. Arnold" <ryan dot arnold at gmail dot com>, "H.J. Lu" <hjl dot tools at gmail dot com>, "Joseph S. Myers" <joseph at codesourcery dot com>
- Date: Fri, 11 May 2012 13:12:56 -0600
- Subject: Re: v2: The GNU C Library 2.16 release plan
- References: <4FAC3FCE.email@example.com> <4FAC86E4.firstname.lastname@example.org> <4FACA80B.email@example.com>
On 05/10/2012 11:47 PM, Allan McRae wrote:
I don't think so. I think Red Hat's 552960 has the most amount of
relevant information, including instructions to hang a system that is
using the pthread_cond_* bits currently on the trunk.
Is there a bug report open for that issue? I found various distribution
ones, but non in the glibc tracker.
Yup. Well known problem. Unfortunately triggering the problem requires
access to poorly acting DNS servers, which is why Uli was never able to
trigger the problem. Fedora is currently using Aurelien's patch.
Apart from that issue, the only patch in the Arch Linux package that is
not flagged for glibc-2.16 is for the assertion error in res_query.c
. This has been around since glibc-2.14 and from memory the patch in
that report is widely used.
We've got a mess of locale fixes and a few other randoms in Fedora that
need to be submitted or resolved upstream. I'm hoping to get that
process rolling soon. Nothing I'd consider terribly critical for 2.16.