From: Julian Graham <joolean@gmail.com>
To: Mark H Weaver <mhw@netris.org>
Cc: Andy Wingo <wingo@pobox.com>, guile-devel <guile-devel@gnu.org>
Subject: Re: Possible infinite loop during compilation in 2.2
Date: Fri, 18 Apr 2014 18:28:19 -0400 [thread overview]
Message-ID: <CANdC_RAsZgyhnqGHwSOD1mjpZKgsz8UqrR-Y3KSpvyzxTtZwLA@mail.gmail.com> (raw)
In-Reply-To: <87vbu648lg.fsf@yeeloong.lan>
Hey Mark,
On Fri, Apr 18, 2014 at 5:43 PM, Mark H Weaver <mhw@netris.org> wrote:
> Does Guile 2.0.11 or current stable-2.0 compile it correctly?
I tested with a 2.0.11 built from source as well as with the stock
Ubuntu 13.10 guile-2.0 package (which is 2.0.9, I think) and they both
compiled it just fine.
prev parent reply other threads:[~2014-04-18 22:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-18 16:05 Possible infinite loop during compilation in 2.2 Julian Graham
2014-04-18 19:20 ` Andy Wingo
2014-04-18 19:21 ` Julian Graham
2014-04-18 19:57 ` Julian Graham
2014-04-18 21:43 ` Mark H Weaver
2014-04-18 22:28 ` Julian Graham [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=CANdC_RAsZgyhnqGHwSOD1mjpZKgsz8UqrR-Y3KSpvyzxTtZwLA@mail.gmail.com \
--to=joolean@gmail.com \
--cc=guile-devel@gnu.org \
--cc=mhw@netris.org \
--cc=wingo@pobox.com \
/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).