Re: license relaxation request

2011-10-17 Thread Eric Blake
On 10/17/2011 05:58 PM, Bruno Haible wrote: Hi Eric, Can we relax the license of the following modules from LGPLv3+ down to LGPLv2+, so that libvirt can use them, and on the grounds that they are shipped as part of LGPLv2+ glibc? grantpt unlockpt pt_chown ptsname ttyname_r This is fine with

Re: license relaxation request

2011-10-17 Thread Bruno Haible
Hi Eric, > Can we relax the license of the following modules from LGPLv3+ down to > LGPLv2+, so that libvirt can use them, and on the grounds that they are > shipped as part of LGPLv2+ glibc? > > grantpt > unlockpt > pt_chown > ptsname > ttyname_r This is fine with me. ttyname_r is written by

license relaxation request

2011-10-17 Thread Eric Blake
Can we relax the license of the following modules from LGPLv3+ down to LGPLv2+, so that libvirt can use them, and on the grounds that they are shipped as part of LGPLv2+ glibc? I'm also planning on adding a posix_openpt module. grantpt unlockpt pt_chown ptsname ttyname_r -- Eric Blake ebl.

Re: [PATCH 4/5] crypto libraries: use stdalign

2011-10-17 Thread Bruno Haible
Paul Eggert wrote: > + crypto libraries: use stdalign and > + sys_socket: use stdalign, not alignof Looks fine, because the types involved are neither 'double' nor 'long long'. Bruno -- In memoriam The victims of the French police

Re: [PATCH 2/5] stdalign-tests: new module

2011-10-17 Thread Bruno Haible
Hi Paul, > +# define CHECK_ALIGNAS(type) \ > +type alignas (1 << 3) type##_alignas; \ > +type _Alignas (1 << 3) type##_Alignas; Can we check whether this alignas(8) specifier? I mean, inside main() do if ((uintptr_t) &type##_alignas % (1 << 3) != 0) abort (); The problem is tha

Re: [PATCH 1/5] stdalign: new module

2011-10-17 Thread Bruno Haible
Hi Paul, Thanks for getting back to this. > A while ago Bruno drafted a Gnulib module that is a replacement for C1x. Reference: . > +@item > +@code{_Alignas} and @code{alignas} are not always supported; > +on platforms lacking

Re: porting to NeXTstep

2011-10-17 Thread Daniel Richard G.
I've been playing around with this further, and have some new findings, and a revised patch. * Turns out the problem with -lposix yielding "Floating point exception" is that you're not supposed to link to that library directly; instead, you specify "cc -posix". Akin to -lpthread vs. -pthread.