From: Mumit Khan <khan AT xraylith.wisc.EDU>
To: Pthreads Developers List <pthreads-win32 AT sourceware.cygnus.com>
Subject: Re: What will be in the next snapshot, due soon.
Date: Tue, 14 Sep 1999 20:34:00 -0000 [thread overview]
Message-ID: <199909150227.VAA31806@pluto.xraylith.wisc.edu> (raw)
In-Reply-To: <Pine.LNX.4.05.9909141517040.20967-100000@swan.canberra.edu.au>
Ross Johnson <rpj@ise.canberra.edu.au> writes:
>
> Mumit Khan's patches to enable building the library under
> Mingw32/MSVCRT are in there too.
>
A small clarification -- the patches will allow fully working pthreads
with GCC ix86-pc-mingw32 ports (mingw ports using either CRTDLL or MSVCRT
runtimes), but you'll need to wait till the next release of gcc for it
to actually work.
The changes needed:
- a minor tweak to system header
- a not so minor tweak to make thread-safe C++ exceptions to work with
GCC/Mingw.
I can always make a snapshot available for those who want to play with it,
however with the caveat that certain items may change in the real release
that will break binary compatibility (probably expected when you're used
to dealing with using developer snapshots anyway).
Regards,
Mumit
prev parent reply other threads:[~1999-09-14 20:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-13 23:00 Ross Johnson
1999-09-14 20:34 ` Mumit Khan [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=199909150227.VAA31806@pluto.xraylith.wisc.edu \
--to=pthreads-win32@sourceware.org \
/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).