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