From: Andy Wingo <wingo@pobox.com>
To: Hans Aberg <haberg-1@telia.com>
Cc: "Mark H Weaver" <mhw@netris.org>,
"Ludovic Courtès" <ludo@gnu.org>,
10681@debbugs.gnu.org
Subject: bug#10681: GNU Guile 2.0.5 released
Date: Wed, 01 Feb 2012 15:53:55 +0100 [thread overview]
Message-ID: <87wr86r4e4.fsf@pobox.com> (raw)
In-Reply-To: <F00DEC12-95FF-4B39-9DFB-E6E585E5A5C7@telia.com> (Hans Aberg's message of "Wed, 1 Feb 2012 14:36:32 +0100")
On Wed 01 Feb 2012 14:36, Hans Aberg <haberg-1@telia.com> writes:
> There is no issue with libffi from latest GIT compiled with
> llvm-gcc-4.2, and guile-2.0.5 compiled with SVN gcc-4.7.
But there is an issue with libffi from git compiled with llvm-gcc-4.2,
and guile-2.0.5 compiled with llvm-gcc-4.2?
Can you try compiling libffi from GIT with gcc-4.7, and guile-2.0.5 with
llvm-gcc-4.2?
Just to check :)
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2012-02-01 14:53 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87r4yg3l3e.fsf@gnu.org>
2012-01-31 14:21 ` bug#10681: GNU Guile 2.0.5 released Hans Aberg
2012-01-31 14:40 ` Andy Wingo
2012-01-31 15:04 ` Hans Aberg
2012-01-31 15:18 ` Ludovic Courtès
2012-01-31 16:59 ` Hans Aberg
2012-01-31 18:04 ` Mark H Weaver
2012-01-31 19:30 ` Hans Aberg
2012-01-31 19:35 ` Mark H Weaver
2012-01-31 19:41 ` Hans Aberg
2012-01-31 20:01 ` Hans Aberg
2012-01-31 22:02 ` Hans Aberg
2012-02-01 1:42 ` Mark H Weaver
2012-02-01 9:35 ` Hans Aberg
2012-02-01 14:14 ` Hans Aberg
2012-02-01 1:34 ` Hans Aberg
2012-02-01 1:49 ` Mark H Weaver
2012-02-01 9:18 ` Hans Aberg
2012-02-01 11:50 ` Andy Wingo
2012-02-01 13:36 ` Hans Aberg
2012-02-01 14:53 ` Andy Wingo [this message]
2012-02-01 15:08 ` Hans Aberg
2012-07-06 18:23 ` Andy Wingo
2012-07-07 12:03 ` bug#10681: GNU Guile 2.0.6 released 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=87wr86r4e4.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=10681@debbugs.gnu.org \
--cc=haberg-1@telia.com \
--cc=ludo@gnu.org \
--cc=mhw@netris.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).