From: Kevin Ryde <user42@zip.com.au>
Cc: bug-guile@gnu.org
Subject: Re: [Patch] --with-threads on MinGW
Date: Wed, 27 Dec 2006 11:10:20 +1100 [thread overview]
Message-ID: <87hcvi6vwz.fsf@zip.com.au> (raw)
In-Reply-To: <87slfigg2x.fsf@zip.com.au> (Kevin Ryde's message of "Fri, 15 Dec 2006 11:25:58 +1100")
I made the sigmask change. That should be all of what you reported,
thanks.
But you could give it a run when you get a chance, I'm not sure if
that signal delivery thread will do the right thing. I'm guessing
it'll be harmless but useless. It might be better to go with the null
threads code. The test suite doesn't really exercise signals, you
might have to make your own program with some raises or alarms.
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile
prev parent reply other threads:[~2006-12-27 0:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-03 18:26 [Patch] --with-threads on MinGW Nils Durner
2006-12-04 0:31 ` Kevin Ryde
2006-12-04 21:18 ` Nils Durner
2006-12-13 23:29 ` Kevin Ryde
2006-12-13 23:55 ` Kevin Ryde
2006-12-14 0:09 ` Kevin Ryde
2006-12-14 22:12 ` Nils Durner
2006-12-15 0:24 ` Kevin Ryde
2006-12-14 0:40 ` Kevin Ryde
2006-12-14 0:12 ` Kevin Ryde
2006-12-14 21:42 ` Nils Durner
2006-12-15 0:25 ` Kevin Ryde
2006-12-27 0:10 ` Kevin Ryde [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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87hcvi6vwz.fsf@zip.com.au \
--to=user42@zip.com.au \
--cc=bug-guile@gnu.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).