From: David Mercer <dmercer@al...> - 2007-06-08 17:40:09
I am following Mr. Buß's instructions on building a Windows CLISP version
(http://www.frank-buss.de/lisp/clisp.html). The instructions are really good
and clear, except that I run into an error on the step when I call configure.
test `echo '(print (+ 11 99))' | lisp.exe -B . -Efile UTF-8 -Eterminal UTF-8 -
Emisc 1:1 -norc -q -M lispinit.mem -` = 110 || exit 1
/bin/sh.exe: test: =: unary operator expected
make: *** [check-script] Error 1
I can bypass this error by commenting out line 3190 of src\makemake.in, and I
get no further errors. The rest of the instructions work fine, including
creating the test program message.exe, which runs correctly.
However, CLISP does not seem to work quite right. For instance, I cannot get
the REPL, and calling it with command line options such as "-h", "--help", "--
version", "--license" do nothing. I suspect CLISP is having difficulty
detecting the standard output and input streams, so anything that depends on
Please advise. Thank-you.
From: David Mercer <dmercer@al...> - 2007-06-08 17:53:31
David Mercer <dmercer <at> alum.mit.edu> writes:
. . .
> I run into an error on the step when I call configure.
. . .
I might be an idiot. Perhaps this is what Mr. Buß meant by, "The build fails
at the first 'test' call, if you applied the patch, because the console-less
application doesn't print values to stdout, but the build of the program
istself is completed."
I had read that and thought, "I never applied a patch," so it didn't occur to
me that this line was telling me to expect an error, and that I am, in fact,
building a console-less application. My confusion was that there was never a
step called "apply the patch," though I imagine that is what this line which I
executed is doing:
cat /clisp-2.38.patch | patch -p1
That being said, unless I am not, in fact, an idiot, and that I have not really
discovered the source of my problem, I think you can ignore my original post.