From: Ross Johnson <RossJohnson@homemail.com.au>
To: Pthreads-Win32 list <pthreads-win32@sources.redhat.com>
Subject: New pthreads-w32 releases available: versions 2.0.0 and 1.4.0
Date: Wed, 16 Mar 2005 04:16:00 -0000 [thread overview]
Message-ID: <1110946577.29957.12.camel@desk.home> (raw)
[Please note that the package naming has changed to facilitate the main
development trunk and a back-port branch for version 1.x.x, and to
differentiate release versions from beta versions etc. when
appropriate.]
Announcing two new releases of pthreads-w32:-
pthreads-w32-2-0-0-release
pthreads-w32-1-4-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.0.0
-------------
(2005-03-16)
General
-------
This release represents an ABI change and the DLL version naming has
incremented from 1 to 2, e.g. pthreadVC2.dll.
Version 1.4.0 back-ports the new functionality included in this
release. Please distribute DLLs built from that version with updates
to applications built on pthreads-win32 version 1.x.x.
The package naming has changed, replacing the snapshot date with
the version number + descriptive information. E.g. this
release is "pthreads-w32-2-0-0-release".
Bugs fixed
----------
* pthread_setcancelstate() no longer checks for a pending
async cancel event if the library is using alertable async
cancel. See the README file (Prerequisites section) for info
on adding alertable async cancellation.
New features
------------
* pthread_once() now supports init_routine cancellability.
New tests
---------
* Aggressively test pthread_once() init_routine cancellability.
next reply other threads:[~2005-03-16 4:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-16 4:16 Ross Johnson [this message]
2005-04-26 5:25 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=1110946577.29957.12.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).