Mailing-List:	contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin-developers/>
List-Post:	<mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
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 18:12:40 -0500
From:	Christopher Faylor <cgf AT redhat DOT com>
To:	cygwin-developers AT cygwin DOT com
Subject:	Re: pthread_kill prototype
Message-ID:	<20010320181240.A1433@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>
Mime-Version:	1.0
User-Agent:	Mutt/1.3.11i
In-Reply-To:	<01b101c0b190$02df27c0$0200a8c0@lifelesswks>; from robert.collins@itdomain.com.au on Wed, Mar 21, 2001 at 09:49:23AM +1100

On Wed, Mar 21, 2001 at 09:49:23AM +1100, Robert Collins wrote:
>Chris,
>  what was the verdict on fixing this? pthread_kill is protoyped (and
>implemented) incorrectly in pthread.h & thread.cc (conflicts with
>newlibs sys/signal.h). Looking at doco on the web, the correct answer is
>to change thread.cc, but that will break binary compatibility.

I don't recall this being discussed before.  What is the difference
in prototyping that will break compatibility?  More details, please.

cgf

- Raw text -