From: Kevin Ryde <user42@zip.com.au>
Cc: Guile Development <guile-devel@gnu.org>
Subject: Re: 1.8 branch fails make check?
Date: Sat, 11 Mar 2006 10:32:23 +1100 [thread overview]
Message-ID: <87veulkha0.fsf@zip.com.au> (raw)
In-Reply-To: <87acbxx60s.fsf@ossau.uklinux.net> (Neil Jerram's message of "Fri, 10 Mar 2006 22:57:07 +0000")
Neil Jerram <neil@ossau.uklinux.net> writes:
>
> If it's not just me, how can we have a released product which is
> failing make check on GNU/Linux?
I added those, from a report on bug-guile. They're real bugs, new in
1.8 and wanting attention from an expert in the shared array stuff.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2006-03-10 23:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-10 22:57 1.8 branch fails make check? Neil Jerram
2006-03-10 23:15 ` Neil Jerram
2006-03-10 23:32 ` Kevin Ryde [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=87veulkha0.fsf@zip.com.au \
--to=user42@zip.com.au \
--cc=guile-devel@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).