From: szgyg <szgyg@ludens.elte.hu>
To: cygwin-apps@cygwin.com
Subject: Re: how to manage 2 guile version
Date: Tue, 28 Mar 2017 07:09:00 -0000 [thread overview]
Message-ID: <20170328071146.GE1836@debbie.mshome.net> (raw)
In-Reply-To: <46c991b5-ba66-4c9e-204b-ec17a7b76292@gmail.com>
On Tue, Mar 28, 2017 at 07:50:43AM +0200, Marco Atzeri wrote:
> On 28/03/2017 04:15, Yaakov Selkowitz wrote:
>> On 2016-07-17 12:01, Marco Atzeri wrote:
>>> 2.0.12 build fine, I need just to look on some test failures
>>>
>>> 00-socket.test seems to cause a segfault.
>
> Last week I was planning to just release guile-2.0.14,
> but while the test of guile itself is almost fine I noticed an issue
> when building "make" with it.
>
> Only tested on 64 bits, 'make check' of make fails on all guile tests
> [...]
> no real time in the next month to chase it.
FWIW guile 2.2.0 was released two weeks ago [0]. Mostly works, but it
still has failing tests [1].
szgyg
[0] https://lists.gnu.org/archive/html/guile-devel/2017-03/msg00095.html
[1] https://lists.gnu.org/archive/html/guile-devel/2017-03/msg00066.html
next prev parent reply other threads:[~2017-03-28 7:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-14 20:13 Marco Atzeri
2016-07-14 21:29 ` Yaakov Selkowitz
2016-07-17 17:02 ` Marco Atzeri
2017-03-28 2:16 ` Yaakov Selkowitz
2017-03-28 5:50 ` Marco Atzeri
2017-03-28 7:09 ` szgyg [this message]
2017-03-28 16:01 ` Yaakov Selkowitz
2017-03-28 19:50 ` Marco Atzeri
2017-03-28 21:19 ` Yaakov Selkowitz
2017-03-28 15:34 ` Yaakov Selkowitz
2017-03-28 16:01 ` Marco Atzeri
2017-03-28 16:08 ` Yaakov Selkowitz
2017-04-01 12:30 ` Marco Atzeri
2017-04-03 2:07 ` Yaakov Selkowitz
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=20170328071146.GE1836@debbie.mshome.net \
--to=szgyg@ludens.elte.hu \
--cc=cygwin-apps@cygwin.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).