From: Ross Johnson <rpj@callisto.canberra.edu.au>
To: Axel Bock <news-and-lists@the-me.de>
Cc: pthreads-win32@sources.redhat.com, jg@centerwave.de
Subject: Bad source files in snapshot 2004-05-16 -- was Re: ... [various problems]
Date: Tue, 18 May 2004 07:03:00 -0000 [thread overview]
Message-ID: <40A9B535.9050206@callisto.canberra.edu.au> (raw)
In-Reply-To: <40A8F190.30106@the-me.de>
These are all related to the same two omissions and hopefully fixed now.
I've uploaded new packages - both the self-unpacking zip .exe and the
tar.gz archives - differentiated with the word 'fixed' in the names. CVS
was updated yesterday (my time). I've also removed the bad packages.
The new packages are:-
pthreads-2004-05-16-fixed.exe
pthreads-snap-2004-05-16-fixed.tar.gz
The correct files (implement.h and ptw32_semwait.c) are now also in the
sources directory on the ftp site
ftp://sources.redhat.com/pub/pthreads-win32/
Thanks and apologies.
Ross
Axel Bock wrote:
> Hi,
>
> I'm trying to compile pthreads, but I run into the following problem:
>
> $ make GC
> make CC=gcc CLEANUP_FLAGS="-D__CLEANUP_C" OBJ="attr.o ..." pthreadGC.dll
> make[1]: Entering directory '...'
> make[1]: *** No rule to make target `ptw32_semwait.c', needed by
> `private.o'. Stop.
> make[1]: Leaving directory '...' make: *** [GC] Error 2
>
>
> now I thought this might be a makefile error - but I cannot find one
> (although I'm not the biggest makefile expert running around :-)
>
> can anyone help me with this? would be very helpful .... (of course :-)
>
>
> thanks and greetings,
>
> axel.
>
prev parent reply other threads:[~2004-05-18 7:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-17 17:14 make problem with mingw32 Axel Bock
2004-05-18 7:03 ` 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=40A9B535.9050206@callisto.canberra.edu.au \
--to=rpj@callisto.canberra.edu.au \
--cc=jg@centerwave.de \
--cc=news-and-lists@the-me.de \
--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).