From: Kevin Ryde <user42@zip.com.au>
Cc: bug-guile@gnu.org
Subject: Re: Win32/MinGW port
Date: Mon, 09 Oct 2006 10:46:21 +1000 [thread overview]
Message-ID: <87fydy2u5e.fsf@zip.com.au> (raw)
In-Reply-To: <452781A6.9010408@web.de> (Nils Durner's message of "Sat, 07 Oct 2006 12:29:58 +0200")
Nils Durner <ndurner@web.de> writes:
>
> As there are no signals on Win32, I *think* it is okay to just "ifndef
> MINGW" the code.
That might be worth trying. (But not with ifdef mingw, rather a test
for missing funcs or features. There's already been mingw-specific
conditionals that became bogus because missing bits have since been
added to the system.)
> #include <fcntl.h>
> #define pipe(f) _pipe(f, 1000, _O_BINARY)
Yep, we've got that in another file. It might be worth sticking in
_scm.h to get it everywhere.
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile
prev parent reply other threads:[~2006-10-09 0:46 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
2006-10-09 0:46 ` 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=87fydy2u5e.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).