From: "Neil Jerram" <neiljerram@googlemail.com>
To: "Rob Browning" <rlb@defaultvalue.org>
Cc: Guile Users <guile-user@gnu.org>,
guile-gtk discussions <guile-gtk-general@gnu.org>
Subject: Re: Just in case...
Date: Mon, 4 Aug 2008 11:39:30 +0100 [thread overview]
Message-ID: <49dd78620808040339xacc8e1dm344af6a93350fbc8@mail.gmail.com> (raw)
In-Reply-To: <877ib1mfdu.fsf@raven.defaultvalue.org>
2008/8/1 Rob Browning <rlb@defaultvalue.org>:
>
> OK, I should be uploading packages that include Neil's two patches
> this weekend, if not sooner.
Many thanks for handling this, Rob.
Looking now at the logs at
http://buildd.debian.org/pkg.cgi?pkg=guile-1.8, it seems that:
amd64, arm, armel, mips, mipsel, powerpc, s390: are all good
hppa: is still getting the broken pipe / seg fault when building
guile-procedures.texi
ia64: is getting illegal instruction in test-unwind
i386, m68k, sparc: are unclickable, so I can't tell
The ia64 one is fully understood; you just need to add
http://git.savannah.gnu.org/gitweb/?p=guile.git;a=commit;h=78aa4a8850396801f2e5515565d051b45b4f15b5
The hppa symptom is the same as (mips, mipsel, powerpc) were seeing
before the latest patches. What kind of architecture is hppa? Is
there any chance that the patches somehow didn't take for that arch?
Out of interest, what is the difference between Building and Built statuses?
Regards,
Neil
next prev parent reply other threads:[~2008-08-04 10:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87wsjgnvp3.fsf@gnu.org>
2008-07-25 10:05 ` Summer holidays Neil Jerram
2008-07-25 15:23 ` Just in case Jon Wilson
2008-07-26 15:49 ` Andy Wingo
2008-07-28 9:31 ` Neil Jerram
2008-07-29 8:08 ` Neil Jerram
2008-07-29 9:06 ` Ludovic Courtès
2008-07-30 0:38 ` Rob Browning
2008-08-01 6:13 ` Rob Browning
2008-08-04 10:39 ` Neil Jerram [this message]
2008-08-05 7:15 ` Rob Browning
2008-08-07 21:58 ` Neil Jerram
2008-08-08 1:35 ` Rob Browning
2008-08-11 0:45 ` Rob Browning
2008-08-11 1:08 ` Rob Browning
2008-08-11 1:47 ` Rob Browning
2008-08-11 8:58 ` Neil Jerram
2008-08-12 14:37 ` Neil Jerram
2008-08-12 23:26 ` Rob Browning
2008-08-13 7:36 ` Neil Jerram
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=49dd78620808040339xacc8e1dm344af6a93350fbc8@mail.gmail.com \
--to=neiljerram@googlemail.com \
--cc=guile-gtk-general@gnu.org \
--cc=guile-user@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).