This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: v2: The GNU C Library 2.16 release plan
- From: "Carlos O'Donell" <carlos at systemhalted dot org>
- To: Mike Frysinger <vapier at gentoo dot org>
- Cc: libc-alpha at sourceware dot org, "Joseph S. Myers" <joseph at codesourcery dot com>, "Carlos O'Donell" <carlos_odonell at mentor dot com>, 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>
- Date: Fri, 1 Jun 2012 22:35:13 -0400
- Subject: Re: v2: The GNU C Library 2.16 release plan
- References: <4FAC3FCE.1020402@mentor.com><Pine.LNX.4.64.1205302354240.8161@digraph.polyomino.org.uk><Pine.LNX.4.64.1205311847020.15944@digraph.polyomino.org.uk><201205311551.54950.vapier@gentoo.org>
On Thu, May 31, 2012 at 3:51 PM, Mike Frysinger <vapier@gentoo.org> wrote:
> On Thursday 31 May 2012 14:48:52 Joseph S. Myers wrote:
>> Oh, and one other point about release testing:
>>
>> GCC routinely gets tested before release by full GNU/Linux distribution
>> rebuilds - is anyone able to test distribution rebuilds with new glibc
>> after we freeze for 4.6? ?This may be less likely to show up problems than
>> rebuilds with new GCC are, but it could still be useful.
>
> in testing glibc-2.16 and building up a new chroot, i've noticed two issues:
>
> ?- a lot of gnulib packages fail with gets() errors ... the gnulib project has
> fixed this, but it'll take a while for that to trickle down into all the
> respective projects. ?i've just added patches like this to fix it:
> http://sources.gentoo.org/app-arch/gzip/files/gzip-1.4-no-gets.patch
>
> ?- the fortify warning change wrt optimization is too noisy. ?i glanced
> through gcc to see if the fortify-by-default could be made to work in a
> different way, but couldn't see a clean way of doing it. ?instead, i'll just
> carry this in Gentoo:
Mike,
Thanks for trying everything out!
Is there any way we can come to better consensus around the fortify warnings?
Cheers,
Carlos.