From: chirakara1974 <kiran_divakaran@infosys.com>
To: pthreads-win32@sourceware.org
Subject: pthreads win32 build errors on Microsoft Visual express
Date: Wed, 19 Mar 2008 11:00:00 -0000 [thread overview]
Message-ID: <16142990.post@talk.nabble.com> (raw)
Hi All,
I am using the pthread libs and includes from the below link.
ftp://sourceware.org/pub/pthreads-win32/dll-latest
Have included
pthreadVCE2.lib and
pthreadVCE2.dll
and the
pthread.h , sched.h and semaphore.h in the Microsoft Visual Studio express
paths for include and libraries. I am using a simple threaded program.
But I am getting the below errors , please help me resolve them. Is there
anything else I need to include apart from these .
Any precompiler options and link lines etc. Have added the pthreadVCE2.lib
as well in the additional dependencies option of the linker still the error
are present. Please help.
{{{{------ Build started: Project: Ticktok, Configuration: Debug Win32
------
Linking...
mythread.obj : error LNK2019: unresolved external symbol
__imp__pthread_exit referenced in function _PrintHello
mythread.obj : error LNK2019: unresolved external symbol
__imp__pthread_create referenced in function _main
D:\Express0\Ticktok\Debug\Ticktok.exe : fatal error LNK1120: 2 unresolved
externals
Build log was saved at "file://d:\Express0\Ticktok\Debug\BuildLog.htm"
Ticktok - 3 error(s), 0 warning(s)
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped
==========}}}}
Regards,
Kiran
--
View this message in context: http://www.nabble.com/pthreads-win32-build-errors-on-Microsoft-Visual-express-tp16142990p16142990.html
Sent from the Sourceware - pthreads-win32 list mailing list archive at Nabble.com.
next reply other threads:[~2008-03-19 11:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-19 11:00 chirakara1974 [this message]
2008-03-24 4:20 ` chirakara1974
2008-03-28 10:24 ` chirakara1974
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=16142990.post@talk.nabble.com \
--to=kiran_divakaran@infosys.com \
--cc=pthreads-win32@sourceware.org \
/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).