This is the mail archive of the
mailing list for the glibc project.
Re: [Freedce-devel] pthread_clear_exit_np()
- From: Christoph Hellwig <hch at lst dot de>
- To: thomas dot schuetzkowski at web dot de
- Cc: libc-alpha at sources dot redhat dot com, lukeh at padl dot com, freedce-devel at lists dot sourceforge dot net, opendce at opengroup dot org
- Date: Tue, 25 Apr 2006 19:27:16 +0200
- Subject: Re: [Freedce-devel] pthread_clear_exit_np()
- References: <email@example.com>
On Fri, Apr 21, 2006 at 05:26:44PM +0200, firstname.lastname@example.org wrote:
> Hi Luke,
> > To make this work with libc we need to "un-cancel" a thread.
> > ...
> > Of course, using this in a third-party application is problematic as it
> > depends on internal glibc structures.
> > I know the chances of such an API being added to glibc are about nil, but
> > I thought I'd mention this anyway! :-)
> We thought about adding a detection of the glibc version to autoconf stuff and choose the right version of the function. (see Loic's patch)
> Then of course someone has to maintain this for every new version of glibc. :-(
> This idea was skipped, because no one had the time to do this.
Why do you think you really need glibc? Given how old dce legacy
codebases are you just need a basic libc with your threading model. You
could for example take uclibc as a library that is simple and supports
threading and hack draft 4 posix threads into them. no one forces you
to use glibc for your oddish broken legacy garbage.