From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2132 invoked by alias); 17 May 2004 07:42:04 -0000 Mailing-List: contact pthreads-win32-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: pthreads-win32-owner@sources.redhat.com Received: (qmail 2121 invoked from network); 17 May 2004 07:42:03 -0000 Received: from unknown (HELO mail1.caatoosee.com) (212.222.192.11) by sourceware.org with SMTP; 17 May 2004 07:42:03 -0000 Received: (qmail 23693 invoked from network); 17 May 2004 09:42:01 +0200 Received: from p50861361.dip0.t-ipconnect.de (HELO compi) (80.134.19.97) by 0 with SMTP; 17 May 2004 09:42:01 +0200 Message-ID: <000d01c43be2$8cbde780$c160fea9@compi> From: "Dr. Michael Heitland \(caatoosee ag\)" To: , References: <1084779474.40a86bd279418@mail.atlantis.sk> Subject: Re: New snapshot 2004-05-16 available Date: Mon, 17 May 2004 07:42:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-2" Content-Transfer-Encoding: 7bit X-SW-Source: 2004/txt/msg00064.txt.bz2 Hello, I have the same problems while building pthreads with VC71. Furthermore, I get a syntax error in implement.h DWORD ptw32_RegisterCancelation (PAPCFUNC callback, It seems that windows.h is not properly included. Greetings, Michael Heitland ----- Original Message ----- From: To: Sent: Monday, May 17, 2004 9:37 AM Subject: Re: New snapshot 2004-05-16 available > We are having problems compiling source from cvs: > > - seems that ptw32_semwait.c was not added to the cvs > - PAPCFUNC isn't declared when _WIN32_WINNT isn't declared implement.h:449 > - in pthreads_cancel.c:179, the thread->cancelLock isn't unlocked when > WaitForSingleObject returns anything else than WAIT_TIMEOUT (if it terminates > earlier during pthread_cancel) > > brk > > > Ross Johnson wrote: > > Dear all, > > > > Finally there is a new snapshot available that incorporates 99 percent > > of the issues raised over the past 8 to 9 months, including some that > > had not made it into CVS until today. > > > > http://source.redhat.com/pthreads-win32 > > and > > ftp://sources.redhat.com/pub/pthreads-win32 > > > > > > Here are the main changes: > > > > SNAPSHOT 2004-05-16 > > > > > > > Attempt to add Watcom to the list of compilers that can build the library. > > This failed in the end due to it's non-thread-aware errno. The library > > builds but the test suite fails. See README.Watcom for more details. > > > > Note: This is probably a result of not defining the appropriate macro. > > > > Bug fixes > > > > * Bug and memory leak in sem_init() > > - Alex Blanco > > > > * ptw32_getprocessors() now returns CPU count of 1 for WinCE. > > - James Ewing > > > > * pthread_cond_wait() could be canceled at a point where it should not > > be cancelable. Fixed. > > - Alexander Terekhov > > > > * sem_timedwait() had an incorrect timeout calculation. > > - Philippe Di Cristo > > > > * Fix a memory leak left behind after threads are destroyed. > > - P. van Bruggen > > > > > > New features > > > > * Ported to AMD64. > > - Makoto Kato > > > > * True pre-emptive asynchronous cancelation of threads. This is optional > > and requires that Panagiotis E. Hadjidoukas's QueueUserAPCEx package be > > installed. This package is included in the pthreads-win32 self-unpacking > > Zip archive starting from this snapshot. See the README.txt file inside > > the package for installation details. Many thanks to Panagiotis for his > > assistance in getting the hooks into the library. > > > > Note: If you don't use async cancelation in your application, or don't need > > to cancel threads that are blocked on system resources such as network I/O, > > then the default non-preemptive async cancelation is probably good enough. > > However, pthreads-win32 auto-detects the availability of these components > > at run-time, so you don't need to rebuild the library from source if you > > change your mind later. > > > > All of the advice available in books and elsewhere on the undesirability > > of using async cancelation in any application still stands, but this > > feature is a welcome addition with respect to the library's conformance to > > the POSIX standard. > > > > >