From: Rob Browning <rlb@defaultvalue.org>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: guile 1.8.3 fails to build on sparc
Date: Sat, 21 Jan 2012 13:25:03 -0600 [thread overview]
Message-ID: <87sjj8yi28.fsf@trouble.defaultvalue.org> (raw)
In-Reply-To: <878x1wa0kd.fsf@dellish.bordeaux.inria.fr> ("Ludovic Courtès"'s message of "Thu, 07 Feb 2008 23:01:06 +0100")
ludo@gnu.org (Ludovic Courtès) writes:
> ludo@gnu.org (Ludovic Courtès) writes:
>
>> Rob: Would it be possible for you to try out this patch on one of the
>> Debian SPARC machines?
>
> And here's the patch. ;-)
It looks like that doesn't fix the problem -- it failed on ia64 this
time:
https://buildd.debian.org/status/fetch.php?pkg=guile-1.8&arch=ia64&ver=1.8.8%2B1-7&stamp=1323288478
The bug also appears to affect Guile 2.0 on kfreebsd-i386, s390, and
perhaps others (some archs won't build 2.0 at all yet) see the "last
log" links here:
https://buildd.debian.org/status/package.php?p=guile-2.0&suite=sid
i.e., for the gc.test problem on kfreebsd-i386 and s390:
https://buildd.debian.org/status/fetch.php?pkg=guile-2.0&arch=kfreebsd-i386&ver=2.0.3%2B1-2&stamp=1322025585
https://buildd.debian.org/status/fetch.php?pkg=guile-2.0&arch=s390&ver=2.0.3%2B1-2&stamp=1322025002
Anything else I might try?
Thanks
--
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
next prev parent reply other threads:[~2012-01-21 19:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-27 16:35 guile 1.8.3 fails to build on sparc Kamaraju S Kusumanchi
2007-12-01 17:20 ` Kamaraju S Kusumanchi
2008-01-29 22:52 ` Neil Jerram
2008-02-02 5:33 ` Kamaraju S Kusumanchi
2008-01-29 22:48 ` Neil Jerram
2008-01-31 21:17 ` Greg Troxel
2008-02-01 9:42 ` Ludovic Courtès
2008-02-07 21:53 ` Ludovic Courtès
2008-02-07 22:01 ` Ludovic Courtès
2012-01-21 19:25 ` Rob Browning [this message]
2012-01-27 21:47 ` Ludovic Courtès
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=87sjj8yi28.fsf@trouble.defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=guile-devel@gnu.org \
--cc=ludo@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).