From: Vladimir Zhbanov <vzhbanov@gmail.com>
To: guile-user@gnu.org
Subject: Re: Any New Guile Release Planned ?
Date: Wed, 28 Oct 2015 21:15:33 +0300 [thread overview]
Message-ID: <20151028181533.GA16635@localhost.localdomain> (raw)
In-Reply-To: <87h9lcqjrv.fsf@gnu.org>
On Tue, Oct 27, 2015 at 06:54:44PM +0100, Ludovic Courtès wrote:
> Rafik NACCACHE <rafik.naccache@gmail.com> skribis:
>
> > Is there any new release planned soon?
>
> We’ve been meaning to release 2.0.12, which is mostly bug fixes.
The stable-2.0 guile branch contains changes that some of our users
(that is, users of gEDA/gaf) have been waiting for years, especially
after guile 2.0 became necessary to build our package. I mean those
users who have been waiting for Windows support. (Some of them insist on
moving to using Python instead of Guile these days, since they have been
tired trying to cross-compile with guile-2.0 support.) A while ago I was
eventually able to build our toolkit using only one patch for guile [1]
(almost one-liner, in essence), and several work-around patches for some
of our programs, which can be found at [2] and are actually the same
code blocks (declaring an array and doing its initialisation). I don't
know why the latter patches work (geda-gaf with guile 1.8 worked without
them), however, I am sure the issue is in guile 2.0, though I cannot
even found the culprit by bisecting (because of too many changes in both
guile and geda-gaf repositories). Having said all that, I'd like to see
at least the patch [1] committed before the next guile release in order
to have guile cross-compilation for windows working. Are there any
chances for that?
Thanks,
Vladimir
[1] https://github.com/vzh/minipack/blob/master/patches/guile/0001-MinGW-build-support.patch
[2] https://github.com/vzh/minipack/tree/master/patches/geda-gaf
next prev parent reply other threads:[~2015-10-28 18:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-27 16:37 Any New Guile Release Planned ? Rafik NACCACHE
2015-10-27 17:48 ` Thompson, David
2015-10-27 17:54 ` Ludovic Courtès
2015-10-28 16:58 ` Barry Schwartz
2015-10-28 17:17 ` David Michael
2015-10-29 22:48 ` Ludovic Courtès
2015-10-28 18:15 ` Vladimir Zhbanov [this message]
2015-10-29 15:19 ` Ludovic Courtès
2015-11-02 12:10 ` Vladimir Zhbanov
2015-11-02 13:42 ` Ludovic Courtès
2015-11-03 9:27 ` Vladimir Zhbanov
2015-11-02 15:40 ` Eli Zaretskii
2015-10-29 16:39 ` Eli Zaretskii
2015-11-02 12:21 ` Vladimir Zhbanov
2015-11-02 15:42 ` Eli Zaretskii
2015-11-03 14:29 ` Vladimir Zhbanov
2015-10-29 22:53 ` Mike Gran
2015-11-05 20:08 ` 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=20151028181533.GA16635@localhost.localdomain \
--to=vzhbanov@gmail.com \
--cc=guile-user@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).