On Thursday 16 January 2014 16:15:33 Helge Deller wrote: > On 01/16/2014 10:05 PM, Carlos O'Donell wrote: > > On Thu, Jan 16, 2014 at 3:49 PM, John David Anglin wrote: > >>> This is an ABI break. > >>> > >>> You can't do this without rebuilding userspace. > >>> > >>> You need debian an gentoo onboard to do this ABI break. > >> > >> This would take about a month on Debian, so I'm against. Various bits > >> of kernel code traditionally return EWOULDBLOCK, so any application > >> code that just checks EWOULDBLOCK would fail. > > > > That's not true if, like all other targets, EWOULDBLOCK == AGAIN. It's > > only true on hppa, and that's the problem. > > > > The kernel is completely inconsistent about returning EWOULDBLOCK or > > EAGAIN, and the standards do dictate one or the other so the kernel > > and glibc are correct to use one or the other to match the standard. > > > > However, user applications are equally sloppy about checking the right > > value. > > Guy, do you have actual programs which are currently broken and which don't > check for both? My feeling is, that most programs were fixed, but I might > be wrong... my guess is memcached: https://bugs.gentoo.org/show_bug.cgi?id=498262 -mike
Attachment:
signature.asc
Description: This is a digitally signed message part.
