From: "uGAH man" <snake@drinkordie.com>
To: "pthread" <pthreads-win32@sourceware.cygnus.com>
Subject: Re: borland builder
Date: Tue, 18 Jul 2000 14:27:00 -0000 [thread overview]
Message-ID: <000f01bff0fe$fb894520$4124d6c8@com.br.ugah> (raw)
In-Reply-To: <B148DA6A21DBD311AEEF00104B28C229E113@w5.daf.concentric.net>
----- Original Message -----
From: Chris Olivier <Chriso@VIZTEK.NET>
To: 'uGAH man' <snake@drinkordie.com>
Sent: Tuesday, July 18, 2000 4:57 PM
Subject: RE: borland builder
i did what you said, but it failed somehow
i've been wondering, isnt 4.466 bytes too small for all the pthreads code?
you can assume i used the correct .dll which was distributed in the
pthreads-win32 project.
C:\CBuilder5\Bin> impdef pthreads.def pthread.dll
Borland Impdef Version 3.0.22 Copyright (c) 1991, 2000 Inprise Corporation
C:\CBuilder5\Bin> implib pthread.lib pthread.def
Borland Implib Version 3.0.22 Copyright (c) 1991, 2000 Inprise Corporation
Error : unable to open file
C:\Arquivos de programas\Borland\CBuilder5\Bin>dir.def
PTHREADS DEF 4.466 18-07-00 18:24 pthreads.def
> Do this.
>
> impdef pthreads.def pthreads.dll (or whatever name the dll is)
> implib pthreads.lib pthreads.def
>
> Note: You could normally just use "implib pthreads.lib pthreads.dll", but
> Borland
> has a bug that strips the leading "_" from the last entry. This
workaround
> fixes this problem.
next parent reply other threads:[~2000-07-18 14:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <B148DA6A21DBD311AEEF00104B28C229E113@w5.daf.concentric.net>
2000-07-18 14:27 ` uGAH man [this message]
2003-07-18 2:29 Borland Builder Will Bryant
2003-07-18 7:22 ` Dr. Michael Heitland (caatoosee ag)
2003-07-21 5:51 ` Will Bryant
-- strict thread matches above, loose matches on Subject: below --
2003-06-20 15:18 Francisco Vinotinto
2000-07-18 11:57 borland builder uGAH man
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='000f01bff0fe$fb894520$4124d6c8@com.br.ugah' \
--to=snake@drinkordie.com \
--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).