Menu
▾
▴
[ clisp-Bugs-1628070 ] FFCALL make check fails on i686-apple-darwin8.8.1
|
From: SourceForge.net <no...@so...> - 2007-01-05 21:18:40
|
Bugs item #1628070, was opened at 2007-01-04 19:13 Message generated for change (Comment added) made by hoehle You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101355&aid=1628070&group_id=1355 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: ffcall Group: build problems Status: Open >Resolution: Duplicate Priority: 5 Private: No Submitted By: Dennis Ruffer (druffer) Assigned to: Bruno Haible (haible) Summary: FFCALL make check fails on i686-apple-darwin8.8.1 Initial Comment: 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 ---------------------------------------------------------------------- >Comment By: Jörg Höhle (hoehle) Date: 2007-01-05 22:18 Message: Logged In: YES user_id=377168 Originator: NO This looks like a duplicate of bug #1535284 ---------------------------------------------------------------------- Comment By: Jörg Höhle (hoehle) Date: 2007-01-05 22:18 Message: 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. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101355&aid=1628070&group_id=1355 |