From: Rob Browning <rlb@defaultvalue.org>
Cc: guile-devel@gnu.org, reuter@ipd.uka.de
Subject: Re: ia64 problem
Date: Fri, 12 Sep 2003 18:16:34 -0500 [thread overview]
Message-ID: <87fzj1silp.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <16201.60193.195326.156184@localhost.localdomain> (Han-Wen Nienhuys's message of "Mon, 25 Aug 2003 12:55:29 +0200")
Han-Wen Nienhuys <hanwen@cs.uu.nl> writes:
> BTW, do you think this is a Guile bug or rather a bug in the headers of
> the ia64 headers of the kernel?
I think we have an ok workaround in the debian package that I'll make
sure gets in to guile 1.6.5 before release.
--
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://mail.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2003-09-12 23:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-25 10:55 ia64 problem Han-Wen Nienhuys
2003-09-12 23:16 ` Rob Browning [this message]
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=87fzj1silp.fsf@raven.i.defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=guile-devel@gnu.org \
--cc=reuter@ipd.uka.de \
/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).