From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: 12031-done@debbugs.gnu.org, Rob Browning <rlb@defaultvalue.org>
Subject: bug#12031: Guile 2.0.6 build failure (segfault in test-with-guile-module, etc.)
Date: Tue, 05 Mar 2013 17:24:35 +0100 [thread overview]
Message-ID: <87sj49x1a4.fsf@pobox.com> (raw)
In-Reply-To: <87627sxk9y.fsf@gnu.org> ("Ludovic Courtès"'s message of "Wed, 05 Sep 2012 22:54:49 +0200")
On Wed 05 Sep 2012 22:54, ludo@gnu.org (Ludovic Courtès) writes:
> 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.
>
> FWIW, I cannot reproduce it on armv5tel-unknown-linux-gnueabi with Guile
> v2.0.6-20-gd6bd182 on libgc-7.2pre20110122.
Since 2.0.7 sees to be building fine in Debian, marking this one as
done.
Andy
--
http://wingolog.org/
prev parent reply other threads:[~2013-03-05 16:24 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
2012-09-05 20:54 ` Ludovic Courtès
2013-03-05 16:24 ` Andy Wingo [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=87sj49x1a4.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=12031-done@debbugs.gnu.org \
--cc=ludo@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).