From: Neil Jerram <neiljerram@gmail.com>
To: Nick Cripps <nick.cripps@gmail.com>
Cc: bug-guile@gnu.org
Subject: Re: Test fail in Guile-1.8.5
Date: Tue, 7 Dec 2010 10:43:52 +0000 [thread overview]
Message-ID: <AANLkTi=Nde2rKa6F=B0YnFZzJxiJ8UHtQYGP5jrvc0bV@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimuiqNATt7xP6TQOKxaRHpQAMW4mU-VMs7iKjk7@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 278 bytes --]
On 4 December 2010 22:12, Nick Cripps <nick.cripps@gmail.com> wrote:
> Hi,
> I'm trying to build guile-1.8.5 but, when running make check, one of
> the tests (test-asmobs) fails.
>
>
Why 1.8.5 ? Can you try 1.8.7, which is the latest in the 1.8.x series?
Thanks,
Neil
[-- Attachment #2: Type: text/html, Size: 571 bytes --]
prev parent reply other threads:[~2010-12-07 10:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-04 22:12 Test fail in Guile-1.8.5 Nick Cripps
2010-12-07 9:34 ` Andy Wingo
2010-12-08 5:08 ` Nick Cripps
2010-12-08 10:26 ` Andy Wingo
2010-12-07 10:43 ` Neil Jerram [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='AANLkTi=Nde2rKa6F=B0YnFZzJxiJ8UHtQYGP5jrvc0bV@mail.gmail.com' \
--to=neiljerram@gmail.com \
--cc=bug-guile@gnu.org \
--cc=nick.cripps@gmail.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).