From: Ross Johnson <rpj@ise.canberra.edu.au>
To: Erik Hensema <erik.hensema@group2000.nl>
Cc: "'Pthreads-win32'" <pthreads-win32@sourceware.cygnus.com>
Subject: Re: Building with MSVC
Date: Wed, 27 Oct 1999 03:10:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.05.9910272006520.32293-100000@swan.canberra.edu.au> (raw)
In-Reply-To: <A01E735D4940D311A3850090275559330BA992@NTSRV02>
Hi Erik,
Have a look at buildlib.bat. The options used there work fine. In
particular the link command line is:
<ALL ONE LINE>
cl /LD /Zi *.obj /Fepthread.dll /link /nodefaultlib:libcmt
/implib:pthread.lib msvcrt.lib /def:pthread.def
Cheers.
Ross
On Wed, 27 Oct 1999, Erik Hensema wrote:
> Hi,
>
> I'm new to MSVC 6.0, and I'm trying to build pthread.dll with cl and nmake.
> Compiling is no problem, but linking fails with and undefined reference to
> _beginthreadex and _endthreadex. According to the MSVC documentation, these
> functions should be in msvcrt.lib and libcmt.lib, however, linking with /MD
> or /MT doesn' work.
>
> Any clue?
>
> I've created this makefile:
>
> OBJ=attr.obj cancel.obj cleanup.obj condvar.obj create.obj dll.obj errno.obj
> \
> exit.obj fork.obj global.obj misc.obj mutex.obj private.obj
> rwlock.obj \
> sched.obj semaphore.obj signal.obj sync.obj tsd.obj
>
> OPT=/I. /c /GD
>
> all: pthread.dll
>
> clean:
> del *.dll *.obj
>
> pthread.dll: $(OBJ)
> cl /Fepthread.dll /LD /MT $(OBJ) /link /def:pthread.def
>
> attr.obj: attr.c
> cl $(OPT) attr.c
> [...]
>
> --
> Erik Hensema
> Work: erik.hensema@group2000.nl
> Home: erik@hensema.xs4all.nl
>
+----------------------+---+
| Ross Johnson | | E-Mail: rpj@ise.canberra.edu.au
| Info Sciences and Eng|___|
| University of Canberra | FAX: +61 6 2015227
| PO Box 1 |
| Belconnen ACT 2616 | WWW: http://willow.canberra.edu.au/~rpj/
| AUSTRALIA |
+--------------------------+
prev parent reply other threads:[~1999-10-27 3:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-27 2:54 Erik Hensema
1999-10-27 3:10 ` Ross Johnson [this message]
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=Pine.LNX.4.05.9910272006520.32293-100000@swan.canberra.edu.au \
--to=rpj@ise.canberra.edu.au \
--cc=erik.hensema@group2000.nl \
--cc=pthreads-win32@sourceware.cygnus.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).