From: Klaus Ebbe Grue <grue@di...> - 2006-02-07 21:40:35
(1) Thanks for a wonderful CL implementation.
(2) I have installed clisp many times on many machines but I keep
forgetting how to do, so I have re-read the file unix/INSTALL in the
source distribution many times. And have trouble each time. I list some
problems and some suggestions below.
unix/INSTALL contains an 11-step procedure followed by a step 12 which
explains how to avoid (some of) step 1-8. I suggest to move step 12 up
front. More concretely, I suggest to let unix/INSTALL start something
This file describes the standard installation procedure.
Please do read this entire file before starting
- or, if you are impatient, do as follows:
Download and install GNU libsigsegv and GNU readline
tar -xvf clisp-X.YY.tar
./configure --with-module=rawsock --build build-dir
That will install /usr/local/bin/clisp plus a number of other files
various places in the file system. Special hints for some platforms can be
found in file unix/PLATFORMS.
I also have some comments on individual steps. Unfortunately, I can only
point to problems, not to solutions.
Step 3: Just before "./configure build-dir" exits, ./configure suggests
cd build (= Step 4)
./makemake --with-dynamic-ffi --srcdir=../src > Makefile (= Step 4)
make config.lisp (= Step 6)
vi config.lisp (= Step 6)
make (= Step 7)
make check (= Step 8)
It is confusing that the suggestions from the configure script cover
(some of) steps 4 to 8 in unix/INSTALL and does so with slight variations
so that one has to 'merge' the information from unix/INSTALL with the
suggestion from the configure script.
Step 5: ./configure --list-modules does not seem to work.
Step 6: Step 6 suggests to do "vi config.lisp" but I have been unable to
figure out what changes I should make to config.lisp.
Step 9 tells what one could have done in step 3 (--prefix=...). I suggest
to state that in step 3 instead. I suggest you state in step 3 whether you
recommend --prefix=/usr or --prefix=/usr/local. If you recommend
--prefix=/usr I suggest you make that the default for --prefix when using
I hope at least some of the above is helpful.
From: Klaus Ebbe Grue <grue@di...> - 2006-02-21 07:32:34
I have made a patch which adds a new keyword, :parse-options, to
saveinitmem. If :parse-options is NIL then all argv parameters are passed
untouched to the program as if they were preceeded by an implicit "--". If
:parse-options is T (the default) then the saved image parses options as
usual. :parse-options has no effect when :executable is NIL. Example:
$ (patch clisp-2.38/src ...)
$ ./configure --build kg-build-dir
$ cd kg-build-dir/
$ ./lisp.run -M lispinit.mem -B . -q -norc
> (defun main () (prin1 *args*) (quit))
> (saveinitmem "without-parse-options" :quiet t :norc t
:init-function 'main :executable t :parse-options nil)
> (saveinitmem "with-parse-options" :quiet t :norc t
:init-function 'main :executable t :parse-options t)
$ ./without-parse-options abc
$ ./with-parse-options abc
*** - LOAD: A file with name abc does not exist
Would you be interested in the patch? If yes, how would like to have it? I
have never tried CVS, but I can make a "diff -r", or I could simply put
the patched source on the WWW as a .tar.gz since all changes are clearly
marked by "BEGIN KG-2006-02-20" and "END KG-2006-02-20".