Re: bug#13342: Errors trying to build Guile 2.0.7

Re: bug#13342: Errors trying to build Guile 2.0.7

[Peter Teeson]

[-- Attachment #1: Type: text/plain, Size: 1065 bytes --]

MacOS X 10.7.5 Lion. MacPro 4,1Intel dual CPU quad cores.
I've been away for a while so haven't worked on this. Back now and picking up the thread.

The bug is 13342 (see also 10015 and 10681) triggered by running
make check

> bad return from expression `(f-sum -1 2000 -30000 40000000000)': expected 39999971999; got 39999972255
> FAIL: test-ffi


There are 2 compilers available from Apple for C/C++ 
i686-apple-darwin11-llvm-gcc-4.2 (GCC) 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2336.1.00)
Apple clang version 3.0 (tags/Apple/clang-211.12) (based on LLVM 3.0svn)

I've built a standalone test with both of these compilers and they seem not to be the problem
Using the configure/make/make install is routine. But I am not familiar with the details of the make system.

I built guile-2.0.7 using the default configure/make and have 2 questions:
   (a) How can I find out which compiler/linker combo is used?
   (b) How can I change configure.ac to use the other one? (If that's the right place to make the change)

Thanks…

Peter

[-- Attachment #2: Type: text/html, Size: 1594 bytes --]

Re: bug#13342: Errors trying to build Guile 2.0.7

[Andy Wingo]

On Sat 19 Jan 2013 05:42, Peter Teeson <peter.teeson@me.com> writes:

>     bad return from expression `(f-sum -1 2000 -30000 40000000000)':
>     expected 39999971999; got 39999972255
>     
>     FAIL: test-ffi
>     
>
> There are 2 compilers available from Apple for C/C++ 
> i686-apple-darwin11-llvm-gcc-4.2 (GCC) 4.2.1 (Based on Apple Inc. build
> 5658) (LLVM build 2336.1.00)
> Apple clang version 3.0 (tags/Apple/clang-211.12) (based on LLVM 3.0svn)

IIRC rebuilding libffi with a different compiler helps.  But I don't
recall.  Perhaps Hans Aberg recalls?

> I built guile-2.0.7 using the default configure/make and have 2
> questions:
>    (a) How can I find out which compiler/linker combo is used?

Look at your config.log.

>    (b) How can I change configure.ac to use the other one? (If that's
> the right place to make the change)

./configure ... CC=/path/to/different/cc

Regards,

Andy
-- 
http://wingolog.org/

Re: bug#13342: Errors trying to build Guile 2.0.7

[Peter Teeson]

Hi Andy:
Thanks for your patient help. GNU make and friends is entirely new to me at the detail level.
I did the following (starting from scratch):

(0) Starting with the guile-2.0.7 tar ball
 ./configure && make && make check

This used gcc and had 77 warnings and 1 test failure

bad return from expression `(f-sum -1 2000 -30000 40000000000)': expected 39999971999; got 39999972255
FAIL: test-ffi

(1) Then I did 
make clean && ./configure CC=/usr/bin/clang && make && make check

This used clang and had 87 warnings and 2 test failures

bad return from expression `(f-sum -1 2000 -30000 40000000000)': expected 39999971999; got 39999972255
FAIL: test-ffi

fail: scm_is_unsigned_integer ((- (expt 2 64) 1), 0, 18446744073709551615) == 1
FAIL: test-conversion


(2) Comments:
Many of the warnings were common to both compilers. 
Based on the above tests I still maintain that the compilers are not at fault in their code generation.

Instead I suspect something is amiss in the interpreter.

(3) Next step:
I would like to step through the interpreter as it handles the Scheme/guile code.
Although I looked at the manual I am not sure what to do.

(4) Questions:
  (a) Do I need to build a debug version of guile? 
       I note there is a debug flag that can be set. But I don't know where to set it.

 (b) From previous emails I understand I have to run the meta uninstalled version.
      Ideally I would like to run from the terminal and stop the interpreter before it executes
      the byte code for test-ffi.

      That way one can look at the bytes representing the int8_t and see if the sign bit
      is set and interpreted correctly for this data type.

NOTE: In stdint.h there is a typedef signed char        int8_t

Again thanks for the patient replies and help

respect…

Peter