From: Ross Johnson <rpj@ise.canberra.edu.au>
To: Rob Fanner <rfanner@stonethree.com>
Cc: pthreads-win32@sources.redhat.com
Subject: Re: semaphores
Date: Sun, 02 Jun 2002 21:35:00 -0000 [thread overview]
Message-ID: <3CFAF1ED.900@ise.canberra.edu.au> (raw)
In-Reply-To: <003601c20877$51262520$0c01a8c0@thor>
Rob Fanner wrote:
> this might be a good alternative
>
> if ( ReleaseSemaphore( (*sem)->sem, GREATER_THAN_MAXIMUM_SEM_VALUE,
> &value) )
> {
> *sval = value;
> }
>
> Sorry that I've not hacked this into the source and sent you a correct
> patch, but I'm still not confident with VC++ builds, and
> I'm still a bit clueless as to how to set up a pthreadVCE.lib (which I need)
> as opposed to a pthreadVC.lib (the standard
> build for the distro's .dsp file).
Great! Unless there are any problems with this, it will go into the
next snapshot.
Re pthreadVCE.lib, if you've built the pthreadVC.lib version
successfully using the .dsp file, you should only need to add the
following compiler flags:-
/GX /TP /D__CLEANUP_CXX
to build pthreadVCE.lib/.dll (and change the names of your output
files of course). I don't recall off-hand what /TP does, but it's
included with the other flags in the Makefile. This is what I use
for the pre-built libs.
If you're using pthreadVCE.lib then you should also be defining
__CLEANUP_CXX for your application build, so that the appropriate
sections of pthread.h are included.
You may be interested in reading Q4 and Q5 in the pthreads-win32 FAQ
file at:-
ftp://sources.redhat.com/pub/pthreads-win32/FAQ
or the section "SNAPSHOT 2002-03-02 / Cleanup code default style" at:-
http://sources.redhat.com/pthreads-win32/news.html
This will explain why the build defaults to pthreadVC. For
additional information, the problems/issues have been discussed on
the mailing list a couple of times, the most recent thread starts at:-
http://sources.redhat.com/ml/pthreads-win32/2001/msg00143.html
Regards.
Ross
next prev parent reply other threads:[~2002-06-03 4:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-30 7:49 semaphores Bossom, John
2002-05-30 8:37 ` semaphores Phil Frisbie, Jr.
2002-05-30 9:33 ` semaphores Rob Fanner
2002-05-30 9:38 ` semaphores Rob Fanner
2002-05-30 22:32 ` semaphores Ross Johnson
2002-05-31 0:48 ` semaphores Rob Fanner
2002-06-02 21:35 ` Ross Johnson [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-05 4:25 Semaphores Platzer Wolfgang
2002-05-30 8:49 semaphores Nicolas EDEL
2002-05-30 7:11 semaphores Rob Fanner
1999-04-20 13:08 semaphores Michael Ambrus
1999-04-20 19:16 ` semaphores Ross Johnson
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=3CFAF1ED.900@ise.canberra.edu.au \
--to=rpj@ise.canberra.edu.au \
--cc=pthreads-win32@sources.redhat.com \
--cc=rfanner@stonethree.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).