From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18109 invoked by alias); 29 Apr 2004 11:05:02 -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 17863 invoked from network); 29 Apr 2004 11:04:58 -0000 Received: from unknown (HELO delsyne.ro) (213.157.171.89) by sources.redhat.com with SMTP; 29 Apr 2004 11:04:58 -0000 Received: from firebird ([192.168.100.79]) by delsyne.ro (8.12.8/8.12.8) with SMTP id i3TB4kgG010990; Thu, 29 Apr 2004 14:04:50 +0300 Message-ID: <005301c42dd9$d2eae8a0$4f64a8c0@firebird> From: "George Mardale" To: "Vikas Gandhi" Cc: References: <7D5800A5B6E26644B2EB7A862856B0D410B09EB6@SARASWATI> Subject: Re: problems linking Date: Thu, 29 Apr 2004 11:05:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-SW-Source: 2004/txt/msg00045.txt.bz2 Hi, I tested one example (valid1.c), but the errors are still the same. Any other ideas? Thanks, George. ----- Original Message ----- From: "Vikas Gandhi" To: "George Mardale" Cc: Sent: Thursday, April 29, 2004 7:52 AM Subject: RE: problems linking > Have u been able to compile the tests that come along with pthreads-win32. I > am pretty sure that u'll get your answers there itself. > > --Vikas > > -----Original Message----- > From: pthreads-win32-owner@sources.redhat.com > [mailto:pthreads-win32-owner@sources.redhat.com] On Behalf Of George Mardale > Sent: Wednesday, April 28, 2004 9:29 PM > To: pthreads-win32@sources.redhat.com > Subject: problems linking > > Hi, > > I am having a problem using "POSIX threads for win32" binaries. > > I am porting to wince an unix application which uses posix threads. The > compilation works fine, but the linking phase fails (I use pthreadVCE.lib > for linking). The message is: > ... unresolved external symbol __imp_pthread_cond_wait referenced in ... > > I looked inside pthreadVCE.lib and it seems to have a function called > __imp__pthread_cond_wait. So, there is an extra "_" appearing. > Can you please point me to a solution to fix this problem? > > Best regards, > George.