From: Nils Durner <ndurner@web.de>
Subject: Re: Win32/MinGW port
Date: Sat, 07 Oct 2006 12:29:58 +0200 [thread overview]
Message-ID: <452781A6.9010408@web.de> (raw)
In-Reply-To: <87r6xnu47p.fsf@zip.com.au>
> How bad are the missing bits?
It's not too bad. pthreads-win32 is fairly complete and working.
The mentioned functions are missing because Windows lacks the concept of
signals altogether.
> Should configure reject it because
> there's no pthread_sigmask, or is there something the code can do to
> cope?
As there are no signals on Win32, I *think* it is okay to just "ifndef
MINGW" the code.
Regarding the undefined "pipe()":
the easiest thing to do would be to define pipe() in the following way:
#include <fcntl.h>
#define pipe(f) _pipe(f, 1000, _O_BINARY)
_pipe() takes two additional parameters: size in bytes and file mode.
Note that these pipes are blocking.
Nils
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile
next prev parent reply other threads:[~2006-10-07 10:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-02 18:24 Win32/MinGW port Nils Durner
2006-10-02 20:34 ` Kevin Ryde
2006-10-02 21:24 ` Nils Durner
2006-10-04 22:05 ` Kevin Ryde
2006-10-07 10:29 ` Nils Durner [this message]
2006-10-09 0:46 ` Kevin Ryde
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=452781A6.9010408@web.de \
--to=ndurner@web.de \
/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).