From: Will Bryant <will.bryant@ecosm.com>
To: pthreads-win32@sources.redhat.com
Subject: Re: BCB support (lib+dll)
Date: Thu, 18 Nov 2004 03:44:00 -0000 [thread overview]
Message-ID: <419C1B11.5050800@ecosm.com> (raw)
In-Reply-To: <419BF91E.8080009@callisto.canberra.edu.au>
Ross Johnson wrote:
> Not 'officially' supported, but Will Bryant contributed patches and a
> makefile for BCB (see 'Bmakefile' in the source and tests folders -
> also README.Borland). I'm about to run them again to see where they
> get to (I'm in Linux right now on a dual-boot machine). I'm pretty
> sure the dll builds ok, but I don't recall if it passed all the tests.
It builds cleanly, thx, but I'm currently seeing random segfaults in the
new mutex code when I use them in one of my libraries' multithreading
tests. Still trying to track it down; I'll hopefully be posting some
more info in the next couple of days.
FWIW if there is indeed a problem with the new mutex code, that could
explain the other problems ppl have been posting about in the last day.
Cheers,
Will
prev parent reply other threads:[~2004-11-18 3:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-17 11:51 Gianluca
2004-11-17 15:02 ` Robert Kindred
2004-11-18 1:21 ` Ross Johnson
2004-11-18 3:44 ` Will Bryant [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=419C1B11.5050800@ecosm.com \
--to=will.bryant@ecosm.com \
--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).