From: ludo@gnu.org (Ludovic Courtès)
To: Rob Browning <rlb@defaultvalue.org>
Cc: 12031@debbugs.gnu.org
Subject: bug#12031: Guile 2.0.6 build failure (segfault in test-with-guile-module, etc.)
Date: Mon, 03 Sep 2012 23:07:13 +0200 [thread overview]
Message-ID: <87zk56n7cu.fsf@gnu.org> (raw)
In-Reply-To: <87y5masm7q.fsf@trouble.defaultvalue.org> (Rob Browning's message of "Mon, 23 Jul 2012 07:20:25 -0500")
Hi Rob,
Rob Browning <rlb@defaultvalue.org> skribis:
> There seems to be a problem on armhf (and perhaps also armel). This is
> with Guile 2.0.6 linked against Debian libgc-dev 7.1-9.
I’m currently checking on armv5tel, but I don’t have access to an armhf
box (what’s this?). Do you know of any developer machine available?
The GCC Compile Farm doesn’t have this, AFAICS.
Thanks,
Ludo’.
next prev parent reply other threads:[~2012-09-03 21:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-23 12:20 bug#12031: Guile 2.0.6 build failure (segfault in test-with-guile-module, etc.) Rob Browning
2012-09-03 21:07 ` Ludovic Courtès [this message]
2012-09-05 20:54 ` Ludovic Courtès
2013-03-05 16:24 ` Andy Wingo
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=87zk56n7cu.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=12031@debbugs.gnu.org \
--cc=rlb@defaultvalue.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).