From: Jan Nieuwenhuizen <janneke@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 32579@debbugs.gnu.org
Subject: [bug#32579] [PATCH] gnu: Add guile-mingw 2.2.3.
Date: Mon, 03 Sep 2018 23:43:10 +0200 [thread overview]
Message-ID: <87zhwyfea9.fsf@gnu.org> (raw)
In-Reply-To: <87y3ciuvtv.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Mon, 03 Sep 2018 23:15:08 +0200")
Ludovic Courtès writes:
Hi!
>> I created a mingw32 cross build for guile-2.0 some time ago, expecting
>> to need it real soon for "work" or for LilyPond. Neither need
>> materialized until now; but it very soon.
>>
>> Luckily, I found that Mike Gran did quite some work this spring on their
>> wip-mingw-guile-2.2 branch; so I packaged the latest snapshot.
>
> Does that mean that Guile 2.2.5 will cross-build fine with
> --target=i686-w64-mingw32? (I thought this was already the case
> actually.)
Well, if wip-mingw-guile-2.2 is merged; yes. I'm not sure why that
hasn't happened yet, so there may be issues?
> Ideally Guile fixes that are needed would go to ‘stable-2.2’, and then
> Guix would simply package the corrected version.
Sure!
Greetings
janneke
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com
next prev parent reply other threads:[~2018-09-03 21:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-29 18:58 [bug#32579] [PATCH] gnu: Add guile-mingw 2.2.3 Jan Nieuwenhuizen
2018-09-03 21:15 ` Ludovic Courtès
2018-09-03 21:43 ` Jan Nieuwenhuizen [this message]
2018-09-04 12:12 ` Ludovic Courtès
2018-09-04 15:10 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zhwyfea9.fsf@gnu.org \
--to=janneke@gnu.org \
--cc=32579@debbugs.gnu.org \
--cc=ludo@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.