Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Date:	Wed, 15 Aug 2001 20:03:46 -0700
From:	Wesel <wassdamo AT pacbell DOT net>
Subject:	Re: Condition Variables?
To:	cygwin AT cygwin DOT com
Message-id:	<3B7B3812.E8504546@pacbell.net>
MIME-version:	1.0
X-Mailer:	Mozilla 4.75 [en] (Win98; U)
X-Accept-Language:	en,ja
References:	<3B7ACF4C DOT 2DA7CE0 AT pacbell DOT net>
	<997915312 DOT 20153 DOT 19 DOT camel AT lifelesswks>

Robert Collins wrote:
> 
> Uhmm, a) report the actual bug you are experiencing.

PTHREAD_COND_INITIALIZER is not defined.

> b) in this case AFAIK there is no current bug with single-process
> condition variables. Cygwin doesn't have proper support for shared
> process condition/mutex variables yet.

It is single process.  I'll just remove my use (and attempted
workaround) of the PTHREAD_COND_INITIALIZER macro.  That should fix
everything, by not using the macro at all.  Inconvenient, but apparantly
a necessary evil.

> c) To get a fixed version download a snapshot cygwin dll.

That too?  Alright.  

...

My first test works perfectly.  My more complicated test works great as
well.  I think you've fixed the problem.  :)  Now I can get back to the
full program again.


Wesel

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -