cancellation variant for uClibc?

[Paul Brook]

On Thursday 24 August 2006 02:32, Peter S. Mazinger wrote:
> Hello!
>
> There are 2 ways to go with cancellation support
> 1. use wrapsyscall.c (provide visible __libc_x() in libc, x() in libc
> being not cancellable and use __libc_x() that in libpthread to provide x()
> cancellable (requires proper ordering of libs)
> 2. go the "NPTL/glibc" way and do the cancellation in libc already
>
> old linuxthreads uses 1., nptl branch the latter (new linuxthreads done by
> me uses 1.)
>
> Question to NPTL porters (users of 2.): why are functions duplicated in
> libpthread that are present in libc already (and are already cancellable)?

I think glibc defines them in libpthread because that's what linuxthreads did. 
I'm not sure exactly why, or what (if anything) tries to use the libpthread 
versions.

The arm nptl port does not define these in libpthread at all. Any syscalls 
duplicated in libpthread are IMHO bugs.

There are a few functions where the source is in the libpthread directory, but 
the objects end up in libc.a/.so

Paul