1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
|
-*- Mode: Text -*-
WELCOME TO ILISP.
FIRST INSTALLATION STEP: UNPACKING AND COMPILING.
SECOND INSTALLATION STEP: DIALECT REQUIREMENTS.
ILISP assumes a minimum of CLtL2 compliance. This requirements
immediately clashes with the problems of some KCL-derivativs,
including GCL. Here is a list of known problems for several CL
implementations (we do not know whether there are problems with
Scheme's - please let us know).
o All dialects
Be sure that the variables:
ilisp-binary-extension
ilisp-init-binary-extension
ilisp-binary-command
Have the appropriate value. Older versions of ILISP (< 5.8)
assumed a single CL installation and suggested a change to the
hook 'ilisp-site-hook' in the 'ilisp.emacs' file.
This should not be so anymore.
o KCL, AKCL, Ibuki, GCL, and ECL
- DEFPACKAGE
You need to have your system configured with a
DEFPACKAGE. You can either generate an image which contains
it or you can arrange the init file to load it for you.
You can find a DEFPACKAGE in the AI.Repository of CMU.
- LOOP
Most likely the DEFPACKAGE will require a full fledged LOOP.
The same instructions apply.
o CMUCL
Try to set the variables:
cmulisp-source-directory-regexp
cmulisp-local-source-directory
To sensible values.
o Harlequin
No known extra installation glitches
o Lucid
No known extra installation glitches
o Allegro
No known extra installation glitches
o CLISP
No known extra installation glitches
|
