From: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: guile-devel@gnu.org, Han-Wen <hanwen@cs.uu.nl>
Subject: Re: [PATCH]: Cross building and Cygwin fixes.
Date: Wed, 10 Jul 2002 22:02:06 +0200 [thread overview]
Message-ID: <878z4jnygx.fsf@peder.flower> (raw)
In-Reply-To: <87y9cjl5sg.fsf@zagadka.ping.de> (Marius Vollmer's message of "10 Jul 2002 21:52:15 +0200")
Marius Vollmer <mvo@zagadka.ping.de> writes:
>> > Also, I found that some #include <winsock2.h> statements are still
>> > inside #ifdef __MINGW32__ (fports.c, inet_aton.c). It doesn't do any
>> > harm, but you may want to put them inside #ifdef HAVE_WINSOCK2_H now.
>>
>> Yes, will do that as well.
>
> Nope, didn't. There is more than winsock2.h that is affected by
> __MINGW32__ so I didn't feel comfortable enough to change it since I
> can't test it.
It's not that important. Of course the other stuff inside __MINGW32__
should remain inside __MINGW32__, I just wanted to suggest putting all
winsock includes inside HAVE_WINSOCK2_H, for uniformity's sake.
Jan.
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien | http://www.lilypond.org
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-07-10 20:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-03 16:25 [PATCH]: Cross building and Cygwin fixes Jan Nieuwenhuizen
2002-07-07 20:35 ` Marius Vollmer
2002-07-08 9:04 ` Han-Wen Nienhuys
2002-07-08 18:12 ` Marius Vollmer
2002-07-08 9:52 ` Jan Nieuwenhuizen
2002-07-09 18:08 ` Marius Vollmer
2002-07-10 0:37 ` Jan Nieuwenhuizen
2002-07-10 19:34 ` Marius Vollmer
2002-07-10 19:52 ` Marius Vollmer
2002-07-10 20:02 ` Jan Nieuwenhuizen [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-07-03 17:06 Jan Nieuwenhuizen
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=878z4jnygx.fsf@peder.flower \
--to=janneke@gnu.org \
--cc=guile-devel@gnu.org \
--cc=hanwen@cs.uu.nl \
/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).