From: "Neil Jerram" <neiljerram@googlemail.com>
To: "Kamaraju Kusumanchi" <kamaraju@bluebottle.com>
Cc: guile-devel@gnu.org, Rob Browning <rlb@defaultvalue.org>,
Neil Jerram <neil@ossau.uklinux.net>
Subject: Re: GNU Guile 1.8.4 released
Date: Sat, 24 May 2008 22:19:42 +0100 [thread overview]
Message-ID: <49dd78620805241419i759b6bdch9909a01c51302ccc@mail.gmail.com> (raw)
In-Reply-To: <200805151747.m4FHlP3u028370@mi1.bluebottle.com>
[-- Attachment #1: Type: text/plain, Size: 968 bytes --]
2008/5/15 Kamaraju Kusumanchi <kamaraju@bluebottle.com>:
> Not sure if you have noticed already. The build has failed on ia64 with a
> segmentation fault. Here is the relevant log for ia64
>
>
> http://buildd.debian.org/fetch.cgi?pkg=guile-1.8&arch=ia64&ver=1.8.5%2B1-1&stamp=1210454760&file=log&as=raw
OK, now I'm confused. I looked at the build log for ia64 from here -
http://buildd.debian.org/pkg.cgi?pkg=guile-1.8 - just a few minutes ago,
when responding to another FTBFS report, and I'm sure it said that it was
failing with an Illegal instruction in test-unwind. Is there any reason why
these logs might be changing while I'm looking at them, or am I just going
mad?
On another matter... it looks to me as though the build on alpha is now
good, so I guess we must somehow have fixed the cause of the "wrong type to
apply (#0# . #0#)" problem between 1.8.4 and 1.8.5. Would you agree with
that, or am I misunderstanding the status?
Thanks,
Neil
[-- Attachment #2: Type: text/html, Size: 1645 bytes --]
next prev parent reply other threads:[~2008-05-24 21:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-19 21:45 GNU Guile 1.8.4 released Ludovic Courtès
2008-02-25 22:17 ` Kamaraju S Kusumanchi
[not found] ` <878wyhsxfr.fsf@raven.defaultvalue.org>
[not found] ` <87r6c7xpnl.fsf@ossau.uklinux.net>
[not found] ` <200805151747.m4FHlP3u028370@mi1.bluebottle.com>
2008-05-24 21:19 ` Neil Jerram [this message]
2008-05-28 16:18 ` Kamaraju Kusumanchi
2008-05-29 12:20 ` Ludovic Courtès
2008-05-29 13:07 ` Neil Jerram
2008-05-29 18:35 ` 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=49dd78620805241419i759b6bdch9909a01c51302ccc@mail.gmail.com \
--to=neiljerram@googlemail.com \
--cc=guile-devel@gnu.org \
--cc=kamaraju@bluebottle.com \
--cc=neil@ossau.uklinux.net \
--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).