From: <don...@is...> - 2009-01-19 18:08:53
|
Erik Huelsmann writes: > > ;; Loading file build-abcl.lisp ... > > *** - ZEROP: NIL is not a number > Is that a released CLISP version? I'm using clisp 2.44 and JDK 1.5/1.6 > myself to test our build. Just built with these setups successfully. > Unfortunately, I must admit the Ant build is better tested. This change starts in 2.47. I suggest the test simply be changed to (or (null result)(zerop result)). > You're using a newer clisp and a newer JDK? I'm actually using a newer than released clisp (from cvs) and openjdk from fedora 10. The zerop issue is not the only one. The openjdk javac was also returning non zero: 1. Trace: (RUN-SHELL-COMMAND '"/usr/bin/javac -classpath /tmp/abcl/src:/usr/jre/lib/rt.jar -g -5 -nowarn ReaderMacroFunction.java ... ':DIRECTORY '#P"/tmp/abcl/src/org/armedbear/lisp/") 1. Trace: RUN-SHELL-COMMAND ==> -1 http://clisp.podval.org/impnotes/shell.html says If :STREAM was specified for :INPUT or :OUTPUT, a Lisp STREAM is returned. If :STREAM was specified for both :INPUT and :OUTPUT, three Lisp STREAMs are returned, as for the function EXT:MAKE-PIPE-IO-STREAM. Otherwise, the return value depends on the process termination status: if it exited on a signal or a core-dump, the signal number is returned as a negative INTEGER else, if it ended normally with 0 exit status, NIL is returned; otherwise, the status is returned as a positive INTEGER. So I guess javac exited with signal number 1 - sighup. Whatever that means. As I mentioned, the compile seems to have worked. |