unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Rob Browning <rlb@defaultvalue.org>
Cc: a.rottmann@gmx.at, 351693-forwarded@bugs.debian.org,
	Steve Langasek <vorlon@debian.org>
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	[thread overview]
Message-ID: <87r7243bfh.fsf@trouble.defaultvalue.org> (raw)
In-Reply-To: <20060601010806.GA8248@mauritius.dodds.net> (Steve Langasek's message of "Wed, 31 May 2006 18:08:06 -0700")

Steve Langasek <vorlon@debian.org> 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


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel


       reply	other threads:[~2006-06-04 20:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20060601010806.GA8248@mauritius.dodds.net>
2006-06-04 20:36 ` Rob Browning [this message]
2006-06-16 10:14   ` Bug#351693: guile-1.6: builds on ia64, but causes other packages to FTBFS? Neil Jerram
2006-07-15  3:36     ` Rob Browning
2006-07-15 21:50       ` Rob Browning
2006-07-19  7:05         ` Rob Browning

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=87r7243bfh.fsf@trouble.defaultvalue.org \
    --to=rlb@defaultvalue.org \
    --cc=351693-forwarded@bugs.debian.org \
    --cc=a.rottmann@gmx.at \
    --cc=vorlon@debian.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).