Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com Date: Tue, 20 Mar 2001 19:43:06 -0500 From: Christopher Faylor To: cygwin-developers AT cygwin DOT com Subject: Re: pthread_kill prototype Message-ID: <20010320194306.A1778@redhat.com> Reply-To: cygwin-developers AT cygwin DOT com Mail-Followup-To: cygwin-developers AT cygwin DOT com References: <01b101c0b190$02df27c0$0200a8c0 AT lifelesswks> <20010320181240 DOT A1433 AT redhat DOT com> <01e101c0b194$62fe19f0$0200a8c0 AT lifelesswks> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <01e101c0b194$62fe19f0$0200a8c0@lifelesswks>; from robert.collins@itdomain.com.au on Wed, Mar 21, 2001 at 10:20:42AM +1100 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. I pretty much just kill any message that mentions python now. >pthread_kill is current defined in pthread.h as int >pthread_kill(pthread_t *, int sig); > >it is also defined in sys/signal.h as >int pthread_kill(pthread_t, int sig); > >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