Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#398 FFCALL make check fails on i686-apple-darwin8.8.1

build problems
closed-out-of-date
Bruno Haible
ffcall (13)
5
2008-01-22
2007-01-04
Dennis Ruffer
No

Source/ffcall-1.10 druffer$ make check
cd avcall; make check
./minitests > minitests.out
LC_ALL=C uniq -u < minitests.out > minitests.output.i686-apple-darwin8.8.1
test '!' -s minitests.output.i686-apple-darwin8.8.1
cd vacall; make check
./minitests > minitests.out
LC_ALL=C uniq -u < minitests.out > minitests.output.i686-apple-darwin8.8.1
test '!' -s minitests.output.i686-apple-darwin8.8.1
cd trampoline; make check
./test1
Works, test1 passed.
./test2
test2 passed.
touch tests.passed.i686-apple-darwin8.8.1
cd callback; make check
cd vacall_r; make all
make[2]: Nothing to be done for `all'.
cd trampoline_r; make all
make[2]: Nothing to be done for `all'.
cd vacall_r; make check
make[2]: Nothing to be done for `check'.
cd trampoline_r; make check
./test1
make[2]: *** [check] Illegal instruction
make[1]: *** [check-subdirs] Error 2
make: *** [check] Error 2

Discussion

  • Sam Steingold
    Sam Steingold
    2007-01-04

    • summary: make check fails on i686-apple-darwin8.8.1 --> FFCALL make check fails on i686-apple-darwin8.8.1
     
  • Jörg Höhle
    Jörg Höhle
    2007-01-05

    Logged In: YES
    user_id=377168
    Originator: NO

    This looks like a duplicate of bug #1535284

     
  • Jörg Höhle
    Jörg Höhle
    2007-01-05

    • status: open --> open-duplicate
     
  • Jörg Höhle
    Jörg Höhle
    2007-01-05

    Logged In: YES
    user_id=377168
    Originator: NO

    This bug report is now marked as "pending"/"invalid".
    This means that we think that the problem you report
    is not a problem with CLISP.
    Unless you - the reporter - act within 2 weeks,
    the bug will be permanently closed.
    Sorry about the inconvenience -
    we hope your silence means that
    you agree that this is not a bug in CLISP.

     
  • Dennis Ruffer
    Dennis Ruffer
    2007-01-05

    Logged In: YES
    user_id=576829
    Originator: YES

    Yes, this does appear to be the same problem as 1535284, and it may be more deeply intrenched from further experiments that I have done. There appears to be some sort of memory overlap when it is used for OpenGL calls. When I click the "Default Iconic Windows" in the GLUT Preferences, the window contains garbled snippets of what is on the screen. I hope that might help somewhat, but I am way out of my depth here to know how to debug it further.

     
  • Sam Steingold
    Sam Steingold
    2008-01-22

    • status: open-duplicate --> closed-out-of-date