Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Subject: Re: Condition Variables? From: Robert Collins To: Wesel Cc: cygwin AT cygwin DOT com In-Reply-To: <3B7B3812.E8504546@pacbell.net> References: <3B7ACF4C DOT 2DA7CE0 AT pacbell DOT net> <997915312 DOT 20153 DOT 19 DOT camel AT lifelesswks> <3B7B3812 DOT E8504546 AT pacbell DOT net> Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <997937059.6910.2.camel@robertlinux> Mime-Version: 1.0 X-Mailer: Evolution/0.12 (Preview Release) Date: 16 Aug 2001 14:46:45 +1000 X-OriginalArrivalTime: 16 Aug 2001 04:46:53.0633 (UTC) FILETIME=[7882F310:01C1260E] On 15 Aug 2001 20:03:46 -0700, Wesel wrote: > Robert Collins wrote: > > > > Uhmm, a) report the actual bug you are experiencing. > > PTHREAD_COND_INITIALIZER is not defined. Strange.. I thought that was in 1.3.2. Oh well. Anyway, the static initialisers are the last thing on my list of to-dos for pthreads. There are well-defined dynamic initialisers that can be used, and some thread models (such as the win32 model) don't have any equivalent for static initialisers. > > 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. Thats a must. There are some serious problems "in the kernel" - as opposed to a header file issue which is all the missing macro is. Rob -- 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/