From: Eli Zaretskii <eliz@gnu.org>
To: Andy Wingo <wingo@pobox.com>
Cc: 14361@debbugs.gnu.org, ludo@gnu.org
Subject: bug#14361: Building guile 2.0.9 under mingw + msys
Date: Tue, 21 Jun 2016 15:46:35 +0300 [thread overview]
Message-ID: <83mvme7lqs.fsf@gnu.org> (raw)
In-Reply-To: <8737o77e3n.fsf@pobox.com> (message from Andy Wingo on Mon, 20 Jun 2016 23:19:24 +0200)
> From: Andy Wingo <wingo@pobox.com>
> Cc: 14361-done@debbugs.gnu.org, ludo@gnu.org
> Date: Mon, 20 Jun 2016 23:19:24 +0200
>
> Hi Eli :)
>
> Thank you for your ongoing work on MinGW and Guile, it's really
> appreciated. I just wanted to say that explicitly here, even though I'm
> closing this bug, as I understand that things have progressed a bit in
> these 3 years; anyway. Your work is so valuable to many users. Thanks!
Thanks.
I would be happier, though, if the patch for open-process, whose last
version I submitted here:
https://lists.gnu.org/archive/html/guile-devel/2014-08/msg00015.html
would be admitted to the repository, as it fixes important
functionality that is currently unavailable in the MinGW build with
upstream sources. AFAIR, the last communication about this patch was
here:
https://lists.gnu.org/archive/html/guile-devel/2014-08/msg00024.html
https://lists.gnu.org/archive/html/guile-devel/2014-08/msg00041.html
I pinged about it a month later:
https://lists.gnu.org/archive/html/guile-devel/2014-09/msg00066.html
but got no responses.
next prev parent reply other threads:[~2016-06-21 12:46 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAL+StqnixLW+QwOP2BpZrjnz1wAQjnio9H6P=VM=9Cnn-B2-ng@mail.gmail.com>
2012-01-10 22:00 ` bug#10474: Building guile 2.x under mingw + msys Andy Wingo
[not found] ` <87pqerdxq4.fsf@pobox.com>
2012-01-17 8:09 ` Eli Zaretskii
2012-01-17 18:14 ` Eli Zaretskii
2012-01-18 23:55 ` Ludovic Courtès
2012-01-19 4:04 ` Eli Zaretskii
2012-02-02 0:59 ` Andy Wingo
2012-02-02 3:53 ` Eli Zaretskii
2012-02-02 16:39 ` Ludovic Courtès
2012-02-02 17:14 ` Eli Zaretskii
2012-02-02 17:34 ` Eli Zaretskii
2013-02-18 18:10 ` Andy Wingo
2013-02-18 19:56 ` Eli Zaretskii
2013-02-19 10:44 ` Andy Wingo
2013-02-19 12:55 ` Ludovic Courtès
2013-02-19 13:39 ` Andy Wingo
2013-02-19 17:53 ` Eli Zaretskii
2013-02-19 21:44 ` Andy Wingo
2013-02-20 19:16 ` Eli Zaretskii
2013-02-24 12:08 ` Andy Wingo
2013-02-19 15:47 ` Andy Wingo
2013-02-19 18:00 ` Eli Zaretskii
2013-02-24 13:25 ` Andy Wingo
2013-02-24 15:43 ` Eli Zaretskii
2013-05-07 17:18 ` bug#14361: Building guile 2.0.9 " Eli Zaretskii
2016-06-20 21:19 ` Andy Wingo
2016-06-21 12:46 ` Eli Zaretskii [this message]
2016-06-21 15:06 ` Andy Wingo
2016-06-21 15:42 ` Eli Zaretskii
2016-06-21 20:52 ` Andy Wingo
2016-06-24 9:51 ` Eli Zaretskii
2013-02-19 21:39 ` bug#10474: Building guile 2.x " Andy Wingo
2013-02-20 19:14 ` Eli Zaretskii
2013-02-20 21:57 ` Andy Wingo
2013-02-21 3:49 ` Eli Zaretskii
2013-02-21 8:18 ` Andy Wingo
2012-01-19 17:35 ` Eli Zaretskii
2012-01-21 11:09 ` Eli Zaretskii
2012-01-24 12:27 ` Eli Zaretskii
2012-01-25 21:12 ` Ludovic Courtès
2012-01-26 5:37 ` Eli Zaretskii
2012-01-29 18:30 ` Ludovic Courtès
2012-01-29 19:17 ` Eli Zaretskii
2012-01-29 22:56 ` Ludovic Courtès
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=83mvme7lqs.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=14361@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=wingo@pobox.com \
/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).