This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: glibc 2.18 machine status?
- From: "Carlos O'Donell" <carlos at redhat dot com>
- To: David Miller <davem at davemloft dot net>
- Cc: libc-alpha at sourceware dot org, marcus dot shawcroft at linaro dot org, hjl dot tools at gmail dot com, thomas at codesourcery dot com, roland at hack dot frob dot com, krebbel at linux dot vnet dot ibm dot com, vapier at gentoo dot org, cmetcalf at tilera dot com, schwab at linux-m68k dot org
- Date: Tue, 23 Jul 2013 14:33:20 -0400
- Subject: Re: glibc 2.18 machine status?
- References: <51E5C427 dot 60304 at redhat dot com> <20130716 dot 163637 dot 1424870650844239462 dot davem at davemloft dot net> <20130720 dot 164954 dot 1944984791063795494 dot davem at davemloft dot net> <20130720 dot 170648 dot 1941398822349690832 dot davem at davemloft dot net>
On 07/20/2013 08:06 PM, David Miller wrote:
> From: David Miller <davem@davemloft.net>
> Date: Sat, 20 Jul 2013 16:49:54 -0700 (PDT)
>
>> All that is left are failures of nptl/tst-cancel{4,5}* on 64-bit
>> sparc. They all fail the same way saying "minimum write buffer size
>> too large".
>>
>> Should be easy to fix and looks like just a minor adjustment is
>> needed in these test cases.
>
> The problem is that the minimum socket buffer size has been increased
> in recent kernels, so WRITE_BUFFER_SIZE in these test cases needs to
> bumped up a bit.
>
> I'll make sure I choose a value that works in all cases.
>
David,
Could you please update:
http://sourceware.org/glibc/wiki/Release/2.18#Current_Status
With SPARC/SPARC64 build tools/kernel notes for the release?
Once done I'll cross sparc* off the list as "ready"
Cheers,
Carlos.