From: Andy Wingo <wingo@pobox.com>
To: Ken Raeburn <raeburn@raeburn.org>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: a few proposed patches
Date: Tue, 22 May 2012 10:21:29 +0200 [thread overview]
Message-ID: <87fwasy6ba.fsf@pobox.com> (raw)
In-Reply-To: <87k404y6i0.fsf@pobox.com> (Andy Wingo's message of "Tue, 22 May 2012 10:17:27 +0200")
On Tue 22 May 2012 10:17, Andy Wingo <wingo@pobox.com> writes:
> I don't recall what the end result was, but it could have been a bug in
> a libffi compiled by that libgc.
By that GCC, I meant; which is really an old fork Apple made of GNU GCC.
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2012-05-22 8:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-21 5:45 a few proposed patches Ken Raeburn
2012-05-21 6:41 ` Neil Jerram
2012-05-22 7:54 ` Andy Wingo
2012-05-22 16:51 ` Ken Raeburn
2012-05-22 8:17 ` Andy Wingo
2012-05-22 8:21 ` Andy Wingo [this message]
2012-05-22 16:54 ` Ken Raeburn
2012-05-25 14:56 ` Removing ‘GC_PTR’ Ludovic Courtès
2012-05-25 15:31 ` Using labels-as-values on MacOS X Ludovic Courtès
2012-05-25 16:32 ` Hans Aberg
2012-05-26 12:44 ` Ludovic Courtès
2012-05-26 12:58 ` Hans Aberg
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=87fwasy6ba.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=raeburn@raeburn.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).