Andi Kleen <[EMAIL PROTECTED]> wrote: > On Monday 28 August 2006 16:05, Arnd Bergmann wrote: > > > The patch below should address both these issues, as long as the libc > > has a working implementation of syscall(2).
> I would prefer the _syscall() macros to stay independent of the > actual glibc version. Or what do you do otherwise on a system > with old glibc? Upgrading glibc is normally a major PITA. Could just this macro layer be explicitly BSD (or at least LGPL) licensed? If not, it looks like a SCOX-whining-over-errno.h thing in the making in case somebody wants to build a non-GPL libc on top... -- Dr. Horst H. von Brand User #22616 counter.li.org Departamento de Informatica Fono: +56 32 654431 Universidad Tecnica Federico Santa Maria +56 32 654239 Casilla 110-V, Valparaiso, Chile Fax: +56 32 797513 - To unsubscribe from this list: send the line "unsubscribe linux-arch" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
