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 content-class: urn:content-classes:message Subject: RE: pthread_kill prototype MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Date: Wed, 21 Mar 2001 13:39:22 +1100 X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0 Message-ID: Thread-Topic: pthread_kill prototype Thread-Index: AcCxrY+RMkkioB1FEdW0GQBgCC5/aAAAWPbA From: "Robert Collins" To: Cc: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id VAA10286 > -----Original Message----- > From: Norman Vine [mailto:nhv AT cape DOT com] > Robert Collins writes: > > Norman Vine [mailto:nhv AT cape DOT com] wrote: > >> >> > >> > > > > >Are you up to rebuilding those pacakges? I will be breaking > the ABI by > >fixing this - and it will be fixed this week. > >_POSIX_THREADS is referred to by > >http://www.opengroup.org/onlinepubs/007908799/xsh/threads.htm > l as being > >present on XSI systems. Now as I don't know what an XSI system is, I > >wonder why _POSIX_THREADS showed up for you? > > Python uses _POSIX_THREADS to distinguish pthreads from > other possible thread implementations Yes I realise that - what I don't realise is _why_ that symbol was defined when you were building! Cygwin doesn't define it, and python shouldn't define it. > >I will be defining some of those symbols as I go along, but > until I get > >the time to find a full blown pthreads test suite that'll run under > >cygwin... (Norman if you've got some interest.. hint hint) > > It doesn't have a full blown test suite but GNU PTH has a fully > POXIX compilent pthread package that compiles and seems to > run just fine with Cygwin PTH doesn't integrate in with cygwin behind the scenes, so things like pthread_atfork won't work, and shared memory access to mutex's will be broken as well. Or did you mean that their test suite works? Also are you talking the redhat hosted GNU portable threads for win32? Or a more general library based threads implementation (because these are often userland and as such not actually concurrent. Perhaps a url for the one you are talking about? > > Cheers > > Norman Vine >