This is the mail archive of the
pthreads-win32@sourceware.org
mailing list for the pthreas-win32 project.
Re: pthread_exit and STL problems
- From: Stefan Eilemann <eilemann at gmail dot com>
- To: Ross Johnson <Ross dot Johnson at homemail dot com dot au>
- Cc: Pthreads-Win32 list <pthreads-win32 at sourceware dot org>
- Date: Wed, 31 Jan 2007 10:00:20 +0100
- Subject: Re: pthread_exit and STL problems
- References: <3D7E7834-79B3-4C11-BA29-DBF2821B8B6B@gmail.com> <45BFD127.6040609@homemail.com.au>
On 31. Jan, 2007, at 0:13 , Ross Johnson wrote:
Hello Ross,
My C++ is very limited but I have a couple of general questions and
possibly redundant general comments.
You're using pthreads-win32 2.8.0 but which version of the DLL are
you using, VC or VCE?
I am using pthreadVC2.
Are you building the pthreads library from source? The packaged
dlls are built using VC6 and the BUGS file in the pthreads
distribution refers to problems relating to the VCE dll which may
or may not be VC version specific.
I am using the packaged DLL. Since I am using the VC version, it is my
understanding that this doesn't matter.
Does trying any of the above alternatives avoid the problem?
I've just tried to build the library myself using VC8.0.
Using 'nmake clean VC' path failed, since the resulting library
was referencing msvcrt80.dll, which the executable couldn't find.
Converting the .dsw file in VS2005 and using it resulted in a
usable library - though I am not sure which 'version' I have.
__CLEANUP_C and PTW32_BUILD are defined. Can you enlighten me?
Do I need to define __CLEANUP_C during my build as well? I am
just a bit nervous using a library where I haven't fully grokked
the side effects.
Cheers,
Stefan.
--
http://www.equalizergraphics.com
http://www.linkedin.com/in/eilemann