unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Marius Vollmer <mvo@zagadka.ping.de>
Cc: guile-devel@gnu.org, Han-Wen <hanwen@cs.uu.nl>
Subject: Re: [PATCH]: Cross building and Cygwin fixes.
Date: 10 Jul 2002 21:34:10 +0200	[thread overview]
Message-ID: <87d6tvml71.fsf@zagadka.ping.de> (raw)
In-Reply-To: <87u1n8s9if.fsf@peder.flower>

Jan Nieuwenhuizen <janneke@gnu.org> writes:

> The patch I sent, was [meant to be applied] against
> 
>     02:24:51 fred@peder:~/cvs/guile/guile-core-1.6
>     $ cat CVS/Tag  
>     Tbranch_release-1-6

This is the branch for the 1.5.x and 1.6.x releases, correct.  I think
the 'official' way to check for sticky tags is with "cvs status".
Maybe CVS/Tag is misleading?

> I've tested HEAD with the patch below, and it indeed builds fine.

Ok, I will apply it.

> 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.

_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel


  reply	other threads:[~2002-07-10 19:34 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 [this message]
2002-07-10 19:52           ` Marius Vollmer
2002-07-10 20:02             ` Jan Nieuwenhuizen
  -- 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=87d6tvml71.fsf@zagadka.ping.de \
    --to=mvo@zagadka.ping.de \
    --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).