From: Thomas Pfaff <tpfaff@gmx.net>
To: Ghislain Cottat <ghislain.cottat@wanadoo.fr>
Cc: pthreads-win32@sources.redhat.com
Subject: Re: Unresolved reference _imp__pthread_XXXX
Date: Tue, 27 May 2003 06:41:00 -0000 [thread overview]
Message-ID: <3ED3089F.5070406@gmx.net> (raw)
In-Reply-To: <F0E13277A26BD311944600500454CCD0569121@antarctica.intern.net>
Ghislain Cottat wrote:
> Hello,
>
> Trying to compile a linux project with mingw32 (latests binaries, gcc
> 3.2.3
> and msys 1.0.8, etc.), I could build pthreadGC.dll, as well as all
> tests,
> and run them sucessfully, but when I try to link with my project (the
> build
> process works perfectly with linux), I have undefined reference with
> pthread
> symbols :
>
> g++ -o cnedra.exe -lstdc++ -lpthreadGC kernel/cnedra-kernel.o
> kernel/cnedra-library.o kernel/cnedra-main.o kernel/cnedra-thread.o
> kernel/cnedra-plugin.o
>
Try
g++ -o cnedra.exe kernel/cnedra-kernel.o
kernel/cnedra-library.o kernel/cnedra-main.o kernel/cnedra-thread.o
kernel/cnedra-plugin.o -lpthreadGC
The order is important if you link with GNU ld, you must put your libs
behind the objects. And -lstdc++ is not neccessary if you link with g++.
Thomas
next parent reply other threads:[~2003-05-27 6:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <F0E13277A26BD311944600500454CCD0569121@antarctica.intern.net>
2003-05-27 6:41 ` Thomas Pfaff [this message]
2003-05-27 19:56 ` Unresolved reference _imp__pthread_something Ghislain Cottat
2003-05-26 22:29 Unresolved reference _imp__pthread_XXXX Ghislain Cottat
-- strict thread matches above, loose matches on Subject: below --
2003-05-26 22:22 Ghislain Cottat
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=3ED3089F.5070406@gmx.net \
--to=tpfaff@gmx.net \
--cc=ghislain.cottat@wanadoo.fr \
--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).