From: Ross Johnson <RossJohnson@homemail.com.au>
To: Pthreads-Win32 list <pthreads-win32@sources.redhat.com>
Subject: New pthreads-w32 releases available: versions 2.2.0 and 1.6.0
Date: Mon, 04 Apr 2005 02:45:00 -0000 [thread overview]
Message-ID: <1112582690.15352.9.camel@desk.home> (raw)
Announcing two new releases of pthreads-w32:-
pthreads-w32-2-2-0-release
pthreads-w32-1-6-0-release
Packages are available in self-unpacking zip files (.exe) and gzipped
tar files (.tar.gz) as usual.
See
http://sources.redhat.com/pthreads-win32/
or go directly to:
ftp://sources.redhat.com/pub/pthreads-win32/
Red Hat have a low ftp concurrent user limit. Mirrors are at (available
as they update):
http://sources.redhat.com/mirrors.html
RELEASE 2.2.0
-------------
(2005-04-04)
General
-------
* Added makefile targets to build static link versions of the library.
Both MinGW and MSVC. Please note that this does not imply any change
to the LGPL licensing, which still imposes specific conditions on
distributing software that has been statically linked with this library.
* There is a known bug in pthread_once(). Cancellation of the init_routine
exposes a potential starvation (i.e. deadlock) problem if a waiting thread
has a higher priority than the initting thread. This problem will be fixed
in version 3.0.0 of the library.
Bugs fixed
----------
* Fix integer overrun error in sem_timedwait(). sem_timedwait() is also
used by pthread_cond_timedwait().
Kevin Lussier
* Fix preprocessor directives for static linking.
Dimitar Panayotov
RELEASE 2.2.0
-------------
(2005-04-04)
Backport of features and bug fixes from 2.2.0.
next reply other threads:[~2005-04-04 2:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-04 2:45 Ross Johnson [this message]
2005-04-04 3:20 ` 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=1112582690.15352.9.camel@desk.home \
--to=rossjohnson@homemail.com.au \
--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).