From: Hans Aberg <haberg-1@telia.com>
To: Mark H Weaver <mhw@netris.org>
Cc: 10681@debbugs.gnu.org, "Ludovic Courtès" <ludo@gnu.org>
Subject: bug#10681: GNU Guile 2.0.5 released
Date: Wed, 1 Feb 2012 10:35:30 +0100 [thread overview]
Message-ID: <A620B4A2-5CB4-4A97-91D0-27903F657459@telia.com> (raw)
In-Reply-To: <87pqdze3c0.fsf@netris.org>
On 1 Feb 2012, at 02:42, Mark H Weaver wrote:
> Hans Aberg <haberg-1@telia.com> writes:
>> With gcc-4.7.0 (from SVN), the test-ffi test now passes (libffi from
>> GIT)
>
> Excellent! I guess that this was a libffi bug.
No, I think it is with llvm-gcc, in view of that it remained in that compile (as described in another letter).
>> but I get three other failures.
>>
>> The compiler that is normally used on the system, is llvm-gcc-4.2, and
>> its compile is still running.
>
> Please let us know the results of 'make check' when compiling with
> llvm-gcc-4.2. I'm especially curious to hear whether the bytevector
> tests fail with that compiler as well.
There is no such test with the llvm-gcc compiler, strangely enough: it just produces a few tests. It does not show the header that is shown for gcc-4.7 (below), like this
Hans
From gcc-4.7 compile 'make check':
Totals for this test run:
passes: 34886
failures: 3
unexpected passes: 0
expected failures: 30
unresolved test cases: 29
untested test cases: 1
unsupported test cases: 9
errors: 0
next prev parent reply other threads:[~2012-02-01 9:35 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 [this message]
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
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=A620B4A2-5CB4-4A97-91D0-27903F657459@telia.com \
--to=haberg-1@telia.com \
--cc=10681@debbugs.gnu.org \
--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).