From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19239 invoked by alias); 31 Jan 2007 13:54:09 -0000 Received: (qmail 19224 invoked by uid 22791); 31 Jan 2007 13:54:06 -0000 X-Spam-Check-By: sourceware.org Received: from extavgw3.ball.com (HELO extavgw3.ball.com) (162.18.103.210) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 31 Jan 2007 13:53:55 +0000 Received: from AEROMSG1.AERO.BALL.COM (Not Verified[162.18.82.155]) by extavgw3.ball.com with NetIQ MailMarshal 6.0 Service Pack 1a (v6,0,3,33) id ; Wed, 31 Jan 2007 06:54:32 -0700 Received: from daytonmsg2k3.AERO.BALL.COM ([162.18.199.42]) by AEROMSG1.AERO.BALL.COM with Microsoft SMTPSVC(6.0.3790.1830); Wed, 31 Jan 2007 06:53:48 -0700 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Subject: RE: pthread_exit and STL problems Date: Wed, 31 Jan 2007 13:54:00 -0000 Message-ID: References: <3D7E7834-79B3-4C11-BA29-DBF2821B8B6B@gmail.com> <45BFD127.6040609@homemail.com.au> <3B672DA2-909E-405F-B57C-362BB03F6BB8@gmail.com> From: "Streithorst, Kip" To: "Stefan Eilemann" , "Ross Johnson" Cc: "Pthreads-Win32 list" X-IsSubscribed: yes Mailing-List: contact pthreads-win32-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: pthreads-win32-owner@sourceware.org X-SW-Source: 2007/txt/msg00013.txt.bz2 The reason the executable couldn't locate msvcrt80.dll is because you will have to install the Visual Studio 8 redistributable which can be found in " C:\Program Files (x86)\Microsoft Visual Studio 8\SDK\v2.0\BootStrapper\Packages\vcredist_x86" of a Visual Studio install. Or you can read more at Microsoft's website. The other thing you have to do is embed the manifest into the pthreadVC2.dll after is generated. This is a new requirement Microsoft added for Visual Studio 8.=20 Ross, The embedding of the manifest in the dll is another thing besides the warnings that has to be dealt with. Thanks, Kip -----Original Message----- From: pthreads-win32-owner@sourceware.org [mailto:pthreads-win32-owner@sourceware.org] On Behalf Of Stefan Eilemann Sent: Wednesday, January 31, 2007 4:00 AM To: Ross Johnson Cc: Pthreads-Win32 list Subject: Re: pthread_exit and STL problems 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=20=20 > possibly redundant general comments. > > You're using pthreads-win32 2.8.0 but which version of the DLL are=20=20 > you using, VC or VCE? I am using pthreadVC2. > Are you building the pthreads library from source? The packaged=20=20 > dlls are built using VC6 and the BUGS file in the pthreads=20=20 > distribution refers to problems relating to the VCE dll which may=20=20 > 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. --=20 http://www.equalizergraphics.com http://www.linkedin.com/in/eilemann