[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Bug#351693: guile-1.6: builds on ia64, but causes other packages to
From: |
Rob Browning |
Subject: |
Re: Bug#351693: guile-1.6: builds on ia64, but causes other packages to FTBFS? |
Date: |
Sun, 04 Jun 2006 13:36:50 -0700 |
User-agent: |
Gnus/5.110004 (No Gnus v0.4) Emacs/21.4 (gnu/linux) |
Steve Langasek <address@hidden> writes:
> I see that guile-1.6 1.6.8-2 has now built successfully on ia64 (congrats!),
> but it looks like the first package to try to build *against* it, g-wrap,
> now fails with an error that looks like it's also a guile-1.6 problem:
[...]
> Rob, any ideas on this?
Indeed. I can reproduce this in the sid chroot on merulo and after
some hacking, I've narrowed it down to a problem with Guile's
call-with-current-continuation (which is called by guile-library's
unit-test.scm[1]):
(define (foo)
(call-with-current-continuation
(lambda (return)
(return #t))))
guile> (foo)
Illegal instruction
I'm cc'ing upstream.
[1] Although Guile certainly needs to fix this bug, it looks like it
might be easy to rewrite the unit-test.scm methods without using
call-with-current-continuation, and at least with Guile, that
should make them notably more efficient.
Thanks
--
Rob Browning
rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
- Re: Bug#351693: guile-1.6: builds on ia64, but causes other packages to FTBFS?,
Rob Browning <=