This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: glibc-2.19 - two weeks to go!
- From: Allan McRae <allan at archlinux dot org>
- Cc: libc-alpha <libc-alpha at sourceware dot org>
- Date: Mon, 20 Jan 2014 12:55:18 +1000
- Subject: Re: glibc-2.19 - two weeks to go!
- Authentication-results: sourceware.org; auth=none
- References: <52D92251 dot 4090203 at archlinux dot org> <CAFqB+PwWYrKX=p1vnU9v1u7WPcZtXx+Um17WPgiCXgnC6K-Cow at mail dot gmail dot com>
On 18/01/14 01:03, Marcus Shawcroft wrote:
> On 17 January 2014 12:30, Allan McRae <allan@archlinux.org> wrote:
>> Hi all,
>>
>> glibc-2.19 is scheduled to be released in two weeks today. So lets have
>> a look at the current status.
>>
>> https://sourceware.org/glibc/wiki/Release/2.19
>>
>> Blockers/desirables:
>> - all features listed in the wiki have been either implemented or
>> delayed until 2.20
>> - there are still a few bugs with the 2.19 milestone set [1] .
>>
>> Is BZ#12683 (Race conditions in pthread cancellation) still targeted at
>> 2.19? The Aarch64 issue has a patch submitted and I'm not sure what is
>
> Hi
>
> I'll look at the clone.S CFI directives patch next. The other issue
> w.r.t aarch64 for 2.19 is the lack of consensus over fixing the BE
> loader name.
>
For reference, here is the discussion about BE loader name for aarch64:
https://sourceware.org/ml/libc-ports/2014-01/msg00003.html
Looks like consensus has been reached:
https://sourceware.org/ml/libc-ports/2014-01/msg00036.html
Allan