Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT cygwin DOT com>
List-Help: <mailto:cygwin-developers-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT cygwin DOT com
Delivered-To: mailing list cygwin-developers AT cygwin DOT com
Date: Wed, 22 Jan 2003 10:03:38 -0500
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin-developers AT cygwin DOT com
Subject: Re: ARGH  pthreads tests failing?
Message-ID: <20030122150338.GA4396@redhat.com>
Reply-To: cygwin-developers AT cygwin DOT com
Mail-Followup-To: cygwin-developers AT cygwin DOT com
References: <20030121060921 DOT GA29480 AT redhat DOT com> <Pine DOT WNT DOT 4 DOT 44 DOT 0301221035540 DOT 560-100000 AT algeria DOT intern DOT net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.WNT.4.44.0301221035540.560-100000@algeria.intern.net>
User-Agent: Mutt/1.5.1i

On Wed, Jan 22, 2003 at 10:53:19AM +0100, Thomas Pfaff wrote:
>I can only guess here but it might be that the wrong pthread.h is
>included in your tests. I remember some mails about -include does not
>behave properly with gcc-3, it will always take the headers from
>/usr/include first.

How about a patch, then?

Or, perhaps more importantly, are you saying that you've broken binary
compatibility with previous versions of cygwin?

cgf