pthread_kill prototype

Robert Collins robert.collins@itdomain.com.au
Tue Mar 20 17:04:00 GMT 2001


> -----Original Message-----
> From: Christopher Faylor [ mailto:cgf@redhat.com ]
> Sent: Wednesday, March 21, 2001 11:43 AM
> To: cygwin-developers@cygwin.com
> Subject: Re: pthread_kill prototype
> 
> 
> On Wed, Mar 21, 2001 at 10:20:42AM +1100, Robert Collins wrote:
> > http://sources.redhat.com/ml/cygwin/2001-03/msg01276.html
> 
> Ah.  I stopped reading all of the python nonense a long time ago.  I
> don't know anything about python and watching people continually
> attempting to build it was excruciating.

Same here.... but I realised that I had covered off the problems with
the present functions AFAICT and was looking for a quick list of missing
functions that have bugged people. So I figured I'd add to the misery :]


> 
> I pretty much just kill any message that mentions python now.

python anyone? :]

> 
> >the definition in sys/signal.h is the posixly correct one.
> 
> Then that's the one that we should be using.  Just nuke the old
> one.
> 
> AFAICT, you're the first person to actually try to use the pthread
> stuff and make it work correctly.  If Cygwin's implementation 
> was wrong
> then I don't see how any programs could be ported to it.
> 
> cgf
> 

Well someone may have done
#ifdef __CYGWIN__
  pthread_kill(&var,sig)
#else
 pthread_kill(var,sig)
#endif

but at worst they just have to get rid of that unportable test and
rebuild...

I'll fix that up and start moving around types and so forth in the next
patch...

Rob



More information about the Cygwin-developers mailing list