unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
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: Tue, 31 Jan 2012 21:01:37 +0100	[thread overview]
Message-ID: <6770CBE1-3793-4714-A6BA-2BFE20A77113@telia.com> (raw)
In-Reply-To: <878vknfywv.fsf@netris.org>

On 31 Jan 2012, at 20:35, Mark H Weaver wrote:

>>>> The 'make check' gives this error, on OS X 10.7.2 using the compiler
>>>> i686-apple-darwin11-llvm-gcc-4.2 (GCC) 4.2.1 supplied by Xcode 4.2.1:
>>>> 
>>>> PASS: test-asmobs
>>>> bad return from expression `(f-sum -1 2000 -30000 40000000000)': expected 39999971999; got 39999972255
>>> 
>>> I may be stating the obvious here, but the -1, which is declared to be
>>> of type 'scm_t_int8' in the C function being called, is apparently being
>>> interpreted as 255.  This suggests that whatever is handling its
>>> promotion to a full int is failing to extend its sign bit.  I'm guessing
>>> that this is libffi's job.
>> 
>> It is broken (libffi from GIT, the only that works on OX 10.7):
> 
> You need to install DejaGnu in order to run libffi's test suite.
> <http://www.gnu.org/software/dejagnu/>

It seem they passed (not giving any details).

Hans


Test Run on Tue Jan 31 20:51:33 2012
Native configuration is x86_64-apple-darwin11.2.0

		=== libffi tests ===

Schedule of variations:
    unix

Running target unix
Using /usr/local/share/dejagnu/baseboards/unix.exp as board description file for target.
Using /usr/local/share/dejagnu/config/unix.exp as generic interface file for target.
Using /usr/local/src/libffi/git/libffi/testsuite/config/default.exp as tool-and-target-specific interface file.
Running /usr/local/src/libffi/git/libffi/testsuite/libffi.call/call.exp ...
Running /usr/local/src/libffi/git/libffi/testsuite/libffi.special/special.exp ...

		=== libffi Summary ===

# of expected passes		1659
# of unsupported tests		15
Making check in man
make[1]: Nothing to be done for `check'.
make[1]: Nothing to be done for `check-am'.








  parent reply	other threads:[~2012-01-31 20:01 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 [this message]
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
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=6770CBE1-3793-4714-A6BA-2BFE20A77113@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).