From: "George Mardale" <gix@delsyne.ro>
To: "Vikas Gandhi" <VGandhi@quark.co.in>
Cc: <pthreads-win32@sources.redhat.com>
Subject: Re: problems linking
Date: Fri, 30 Apr 2004 06:32:00 -0000 [thread overview]
Message-ID: <006601c42e7c$f7fe0a20$4f64a8c0@firebird> (raw)
In-Reply-To: <7D5800A5B6E26644B2EB7A862856B0D410BC7642@SARASWATI>
Hi again,
I managed to solve the problem. Thanks to Ross Johnson for pointing out the
correct approach. I use eVC++ and I used the prebuilt binaries, which I
thouhght were for wince, but they weren't.
After recompiling the wince port of pthreads-win32 (+ setting the proper
#define-s), it worked...
Thanks again for your support, guys.
Best regards,
George.
----- Original Message -----
From: "Vikas Gandhi" <VGandhi@quark.co.in>
To: "George Mardale" <gix@delsyne.ro>
Cc: <pthreads-win32@sources.redhat.com>
Sent: Friday, April 30, 2004 7:30 AM
Subject: RE: problems linking
> Please give all your details
> which compiler are u using ?????
> If I remember currently u can also make all the test during build itself
> that too with no issues.
>
> Please give more details what are u trying to do. Mail yr program also.
>
> --Vikas
>
> -----Original Message-----
> From: George Mardale [mailto:gix@delsyne.ro]
> Sent: Thursday, April 29, 2004 4:35 PM
> To: Vikas Gandhi
> Cc: pthreads-win32@sources.redhat.com
> Subject: Re: problems linking
>
> Hi,
>
> I tested one example (valid1.c), but the errors are still the same.
> Any other ideas?
>
> Thanks,
> George.
>
> ----- Original Message -----
> From: "Vikas Gandhi" <VGandhi@quark.co.in>
> To: "George Mardale" <gix@delsyne.ro>
> Cc: <pthreads-win32@sources.redhat.com>
> 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.
next prev parent reply other threads:[~2004-04-30 6:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-30 4:32 Vikas Gandhi
2004-04-30 6:32 ` George Mardale [this message]
[not found] ` <40930DE0.6040609@callisto.canberra.edu.au>
2004-05-03 6:25 ` George Mardale
-- strict thread matches above, loose matches on Subject: below --
2004-04-29 4:57 Vikas Gandhi
2004-04-29 11:05 ` 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='006601c42e7c$f7fe0a20$4f64a8c0@firebird' \
--to=gix@delsyne.ro \
--cc=VGandhi@quark.co.in \
--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).