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
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
|
Installation on Unix:
---------------------
This file describes the standard installation procedure. Special hints for
some platforms can be found in file unix/PLATFORMS.
1. (Optional)
Choose which C compiler to use for building CLISP.
This is normally not necessary; if GNU C is available under the
name "gcc", it will be used.
For example, if you were wanting to use gcc with full warnings, then
type, if you are using csh:
setenv CC "gcc -Wall"
or if you are using bash or ksh:
export CC="gcc -Wall"
or if you are using sh:
CC="gcc -Wall"
export CC
2. Choose the name of a directory in which to build CLISP.
(This allows you to build CLISP with different compilers on the same
machine or for different architectures in the same filesystem, sharing
the same source.)
For example, depending on the chosen compiler, let's use with-gcc-wall.
Then execute
./configure with-gcc-wall
This will prepare a directory with-gcc-wall/ and figure out many
system and compiler dependent parameters needed by CLISP.
(Note: Some `make's - for example the HP-UX make - have problems
with symbolic links. You may avoid these by calling
./configure
without argument. Then CLISP will be built in the src/ directory
itself.)
Note that the argument to configure can be an absolute pathname.
For example, the following command will also work.
./configure /tmp/with-gcc-wall
3. The previous step printed a recommendation how to continue. Follow
the recommendation: Go to this directory
cd with-gcc-wall
and build the makefile that controls compilation:
./makemake > Makefile
If you wish to compile the sources such that you may debug them,
then type instead:
./makemake debug > Makefile
The makemake command also accepts a couple of --with-PACKAGE options.
To get a list of the supported options, try
./makemake --help
4. If you wish to build CLISP with add-on modules, edit Makefile and change
the line defining the MODULES variable.
5. Type
make config.lisp
and edit the contents of config.lisp appropriately for your site,
especially the definitions of short-site-name and long-site-name.
If you have unpacked some add-on modules (see the main INSTALL file for
a list), you may choose to build clisp with them. Just add the module
directories to the line defining MODULES in the makefile.
For platform specific adjustment of the makefile, take a look at the
PLATFORMS file.
6. Type
make
to build CLISP.
If you are an expert in building CLISP, you may alternatively do this
in seven steps:
make init prepares all symbolic links and utilities
make allc makes all *.c files
make libreadline.a makes the readline library (not needed
if --with-noreadline was specified)
make lisp.run makes the executable
make interpreted.mem a memory image with everything uncompiled
make halfcompiled.mem a memory image with compiler.fas and
the rest uncompiled
make lispinit.mem makes all *.fas files and
a memory image with everything compiled
make manual makes the documentation
make modular makes the base module set (only needed
if --with-dynamic-ffi was specified)
The sixth step is the most time consuming: it takes an hour on a Sun4 and
may take several hours on a slower machine.
If something goes wrong, check and optionally modify the contents of
the file unixconf.h and retry this step. Yes, there are many warnings,
we know. Most of them are harmless.
If you need to switch to a different compiler, execute a
make distclean
cd ..
and go back to step 1.
7. (Optionally)
Two more tests for CLISP. Let the compiler (now compiled!) recompile itself:
make test
Check whether CLISP passes the test suite:
make testsuite
8. Edit the `prefix' variable in the makefile (you could also have specified
it as command line option --prefix=... to `configure' in step 2), then type
make install
If `prefix' is /usr/local, then this will install the CLISP binaries
into /usr/local/bin and /usr/local/lib (creating a directory
/usr/local/lib/clisp) and the manual page into /usr/local/man/man1.
You may need superuser privileges for this step when installing into
public directories.
If you built with modules (e.g., ./configure --with-module=regexp)
there will be two "linking sets" in /usr/local/lib/clisp/ - "base"
and "full" (see <http://clisp.cons.org/impnotes.html#modules>).
You can chose which liking set to run by using "-K" option of clisp
(see <http://clisp.cons.org/clisp.html#opt-link-set>)
9. If you want other people to benefit from your work, you can make a binary
distribution of CLISP for your platform which we will distribute.
To do this, make sure you have executed step 6 above, adjust the definitions
of ROFF_MAN, PACK, PACKOPT, PACKEXT in the makefile, then type
make distrib
to create a binary distribution in a clisp-*.tar.gz file.
Tell us about your success, and make that file available to us.
If you want to distribute the binaries, recall that you have to accompany
them with full source; see the files COPYING and GNU-GPL.
10. The last thing to do:
cd ..
Authors:
--------
Bruno Haible
Michael Stoll
Email: clisp-list@lists.sourceforge.net
|
