public inbox for pthreads-win32@sourceware.org
 help / color / mirror / Atom feed
From: Vikas Gandhi <VGandhi@quark.co.in>
To: George Mardale <gix@delsyne.ro>
Cc: pthreads-win32@sources.redhat.com
Subject: RE: problems linking
Date: Thu, 29 Apr 2004 04:57:00 -0000	[thread overview]
Message-ID: <7D5800A5B6E26644B2EB7A862856B0D410B09EB6@SARASWATI> (raw)

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.

             reply	other threads:[~2004-04-29  4:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-29  4:57 Vikas Gandhi [this message]
2004-04-29 11:05 ` George Mardale
  -- strict thread matches above, loose matches on Subject: below --
2004-04-30  4:32 Vikas Gandhi
2004-04-30  6:32 ` George Mardale
     [not found]   ` <40930DE0.6040609@callisto.canberra.edu.au>
2004-05-03  6:25     ` George Mardale
2004-04-28 15:59 George Mardale

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7D5800A5B6E26644B2EB7A862856B0D410B09EB6@SARASWATI \
    --to=vgandhi@quark.co.in \
    --cc=gix@delsyne.ro \
    --cc=pthreads-win32@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).