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 sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com Message-Id: <199912081632.KAA07943@mercury.xraylith.wisc.edu> To: John Fortin cc: "cygwin-developers AT sourceware DOT cygnus DOT com" Subject: Re: pthreads status? [was Re: [Fwd: Many changes in latest snapshot]] In-Reply-To: Your message of "Wed, 08 Dec 1999 10:36:45 EST." <384E7B0D DOT 9E23CC6E AT ibm DOT net> Date: Wed, 08 Dec 1999 10:32:19 -0600 From: Mumit Khan John Fortin writes: > > I seem to recall from the pthreads-win32 webpage that win95/98 are not > supported because > of the following... ( from http://sourceware.cygnus.com/pthreads-win32/ ) > The latter two need to be built on Win NT before they will be able to > link applications which use > pthreads-win32. This is because the Win95 kernel32.dll does not include > the functions _beginthreadex and > _endthreadex. Should be fixed by now ... the *threadex functions are exported by MSVCRT DLL, not CRTDLL. Either way, not usable by Cygwin. > Also note that neither Cygwin nor Mingw32 are able to build the library > at this point because they lack > thread-safe exception handling in g++ (the library uses exceptions and > so building with gcc, although the > code should compile, is not recommended if you want proper behaviour). I added thread-safe C++ exceptions to Mingw32, and pthreads-win32 now works like a charm. > I do my coding on Win98, so I can't compile the code. I can't comment on > the g++ exception handling. I ran all the tests on my laptop, which runs Win98. See, things do change for the better ;-> Regards, Mumit