-
Notifications
You must be signed in to change notification settings - Fork 0
/
README.cmucl
55 lines (33 loc) · 1.65 KB
/
README.cmucl
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
Hey emacs, this is -*- text -*-
CMU Common Lisp-specific requirements
0. Executive summary
To begin, just load INSTALL.lisp. Then, load
aserve/examples/examples.cl and start the server with
(net.aserve:start :port 8080)
If you experience problems or want to get rid of some annoying
warnings, read on.
1. Man, this is S_L_O_W! This is unusable!
Chances are you are an experienced user and loaded aserve through
asdf (see next section on some words about that) instead of loading
INSTALL.lisp. If so, you will likely be experiencing request
answer times of about 1 second -- per request, so you can see these
1 pixel transparent GIFs arrive one after the other ...
Take a look at INSTALL.lisp or the function
cl-user::init-aserve-cmu in aserve.asd. Once the multiprocessing
is initialized by one of these methods, the server will be quite a
bit more responsive.
2. Gray streams
Portable Allegroserve needs Gray stream support in the Lisp image
it's running in. The file acl-compat.asd should load the required
files automatically, if gray streams are not yet present in the
Lisp image during system compile / load. If you experience
problems, please report them to the portableaserve mailing list; be
sure to include your version of cmucl, where you obtained it, where
its files are placed in your system, etc. Failing to cleanly load
acl-compat.asd is considered a bug; don't hesitate to report it as
such. As it is, users reported success both on Debian systems and
with the cmucl distribution from cons.org, so it will likely Just
Work (tm).
Have fun,
Rudi Schlatte