unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Jan Nieuwenhuizen <janneke@gnu.org>
To: Christoph Buck <christoph.buck@smartoptics.de>
Cc: guile-devel@gnu.org
Subject: Re: Compiling guile-2.2.4 for mingw
Date: Tue, 20 Nov 2018 18:53:27 +0100	[thread overview]
Message-ID: <87muq3octk.fsf@gnu.org> (raw)
In-Reply-To: <xxt7eh7lt1e.fsf@smartoptics.de> (Christoph Buck's message of "Tue, 20 Nov 2018 15:31:25 +0100")

Christoph Buck writes:

> Currently i try to compile guile-2.2.4 under mingw64 bit.

Oh, interesting!

> I had some minor issues in the c source code which i managed to fix by
> applying some of the patches from
> https://github.com/mkeeter/guile-mingw. Namely
>
> 1) 0003-winsock-compat.mingw.patch
> 2) 0004-start_child.mingw.patch

What is the relation with or status of the wip-mingw-guile branch on
savannah?

    http://git.savannah.gnu.org/cgit/guile.git/log/?h=wip-mingw-guile-2.2

Does this build on top of that, what would be needed to get
wip-mingw-guile merged?

janneke

-- 
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com



      parent reply	other threads:[~2018-11-20 17:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-20 14:31 Compiling guile-2.2.4 for mingw Christoph Buck
2018-11-20 15:39 ` tomas
2018-11-20 15:59 ` Mike Gran
2018-11-20 17:16   ` Christoph Buck
2018-11-20 17:45     ` Mike Gran
2018-11-20 20:27       ` Mark H Weaver
2018-11-20 17:10 ` Eli Zaretskii
2018-11-20 17:53 ` Jan Nieuwenhuizen [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=87muq3octk.fsf@gnu.org \
    --to=janneke@gnu.org \
    --cc=christoph.buck@smartoptics.de \
    --cc=guile-devel@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).