I installed the proper compiler subsystem.
Thanks anyway.
My thank-you mail kept bouncing, so i'm posting.
The GNU Common Lisp can be found at fireant.ma.utexas.edu
in the pub/gcl directory.
Here a copy of the README file.
------------------------------------------------------------------------------
Description of GCL (GNU Common Lisp) system.
OVERVIEW:
The GCL system contains C and lisp source files to build a common lisp
sytem. The original KCL system was written by Taiichi Yuasa and
Masami Hagiya in 1984. The AKCL system work was begun in 1987 by
William Schelter and continued through 1994. A number of people
have contributed ports and pieces. The file doc/contributors lists
some of these. In 1994 AKCL was released as GCL (GNU Common Lisp) the
GNU public library license. Version akcl-1-624 was the last version
made under the old license and using the old file change mechanism.
This readme only applies to versions gcl.1.0 and later. The GNU library
license does allow redistribution of executables containing GCL as
well as users proprietary code, but such redistribution must be
accompanied by sufficient material (eg .o files) to allow recipients
to rebuild an executable, after possibly modifying GCL. See the GNU
file COPYING.LIB-2.0 for a full description of your right to copy this
software.
OBTAINING SOURCES:
-----------------
* There are source files on math.utexas.edu:pub/gcl/gcl.x.x.tgz You
probably want the highest XX version number. For example gcl.1.0.tgz
would allow you to build the version 1.0 of GCL. In the following
this compressed tar file is simply referred to as gcl.tgz. An
alternate source for these files is ftp.cli.com:pub/gcl/gcl-XX.tgz If you
do not have gzip it is available in the directory
···········@prep.ai.mit.edu:/u2/emacs .
GCL will also be available on prep.ai.mit.edu
MAKING THE SYSTEM:
==================
To make the whole system, if you have obtained gcl.tgz.
UNCOMPRESS and UNTAR the SOURCES:
--------------------------------
Change to a directory in which you wish to put gcl, eg /usr/local,
which we shall call PREFIX-DIR.
Copy the file gcl.tgz to the PREFIX-DIR.
% gzip -dc gcl.tgz | tar xvf -
This will create the directory ${PREFIX-DIR}/gcl-1.xxx with
all the sources in it
ADD MACHINE DEFINITIONS TO MAKEFILES:
------------------------------------
Determine the NAME of your machine by looking in the MACHINES file (eg
sun3-os4).
% cd gcl-1.xxx
% add-defs sun3-os4
You should finally be ready to go!
RUNNING MAKE:
------------
% make
The make should continue without error. There may be occasional
warnings from the C compiler, but all files should compile successfully
producing .o files.
At the end you should see a message at the end "Make of GCL xxx
completed", where xxx stands for the version number.
TRY IT OUT:
----------
When it has finally finished you may invoke GCL by using
% xbin/gcl
GCL (GNU Common Lisp) Version(1.0) Apr 21 00:52:31 CDT 1994
Contains Enhancements by W. Schelter
>(+ 2 3)
>5
COPY THE COMMAND SCRIPT:
-----------------------
* You should copy xbin/kcl to /usr/local/bin or some place on users
search paths. This is so that users may conveniently invoke the saved
image with a first arg equal to the directory where the image resides.
(some things like faslink, autoload,.. need to know the system directory).
INSTALLING:
----------
To install under /usr/local do
make install
To specify an alternate directory such as /lusr
do
make install PREFIX_DIR=/lusr
The default installation puts a full executable in
/usr/local/lib/gcl-version/unixport/saved_gcl
and some doc in
/usr/local/lib/gcl-version/doc/
and some autoloading files in
/usr/local/lib/gcl-version/lsp
and a shell script in /usr/local/lib/gcl-version/xbin/gcl
This script is also copied to
/usr/local/bin
FUTURE DIRECTIONS
(and how you may be able to help) Volunteers should contact
William Schelter (···@math.utexas.edu)
a) Upgrading to comply with the forthcoming ANSI standard. Work
needs to be done.
b) Need work on providing a high level window interface. One possible
way would be a good connection with TCL/TK. Another would be to go
in the direction of CLIM.
A new compiler has been written, which is closer to the ANSI standard
and provides some other benefits. It will be in a future release.
We will need people willing to beta test and isolate any bugs.
DOCUMENTATION:
==============
If you use gnu emacs, a convenient method for viewing documentation
of common lisp functions (or functions in an extended system), is
provided by the doc/find-doc.el file. This will be installed when you
do make in the doc directory. Adding the following to your .emacs
file will allow you to use C-h d to find documentation.
(autoload 'find-doc "find-doc" nil t)
(global-set-key "d" 'find-doc)
(visit-doc-file "/usr/local/lib/gcl/doc/DOC")
See the file find-doc.el for more information.
Otherwise you may use the describe command inside lisp.
For example (describe 'print) will print out information about
print. You may also peruse the file doc/DOC.
TROUBLE SHOOTING (some common problems reported):
----------------
1) Did you extract the files with the original write dates--make
depends heavily on this?
2) Did you use -O on a compiler which puts out bad code? Any time you
change the settings or use a new c compiler this is a tricky point.
3) A sample transcript from a correct make is included under
doc/sample-make. If yours compiles less often or does things
differently, something is wrong, probably with dates or the clock on
the server or something.
4) If you can't save an image, try doing so on the file server rather
than a client.
5) Doing the make on a client with the main files on a server, has
sometimes caused random breakage. The large temp files used by the C
compiler seem to sometimes get transferred incorrectly. Solution: use
the server for the compile.
6) Did you make changes in the .defs or .h files, other than just
commenting out a CC=gcc line?
7) Did you read the recommendations in the XXXX.defs file on what
C compiler versions work?
CHANGING THINGS: MAYBE EDIT TWO FILES:
--------------------
Normally you should not need to edit ANY files. There may be some
parameter sizes you wish to change or if you don't have gcc where
we have made that the default, then see CC below.
EDIT the appropriate h/NAME.defs file. These are definitions to
be included in the various makefiles.
For example if the `NAME' of your machine is sun3-os4.
% emacs h/sun3-os4.defs
* CC: set C compiler options. For example, if you are using the GNU
C compiler:
CC = gcc -msoft-float -DVOL=volatile -I$(GCLDIR)/o
Or, if you are using the conventional UNIX C compiler:
CC = cc -DVOL= -I. -I$(GCLDIR)/o
* ODIR_DEBUG:
ODIR_DEBUG= -g
If you want files in the main c source compiled with debugging
information. Note this is incompatible with OFLAGS= -O on
some compilers. Size will be smaller without -g, but you
are then helpless in the face of problems.
* INITFORM: The normal thing is to just have the one form
required for fast loading.
INITFORM=(si::build-symbol-table)
-----------
EDIT the file h/NAME.h (eg h/sun3-os4.h)
(Actually you probably don't need to change it)
This file will be included by virtually every compilation of C
files, except the translated C produced by kcl.
% emacs h/sun3-os4.h
if you wish to change a parameter such as MAXPAGE 16384 established
in bsd.h (ie. number of 2000 byte pages you want as your absolute max
swap space). MAXPAGE must be a power of 2.
#undef MAXPAGE
#define MAXPAGE (2 * 16384)
You may similarly redefine VSSIZE the maximum size for the value
stack (running very deep recursion interpreted may well require this).
DISCLAIMER:
----------
W. Schelter, the University of Texas, and other parties provide this
program on an "as is" basis without warranty of any kind, either
expressed or implied, including, but not limited to, the implied
warranties of merchantability and fitness for a particular purpose.
Bill Schelter
···@math.utexas.edu
See the file doc/contributors for a partial list of people who have
made helpful contributions to ports etc.
-------------------------------------------------------------------------------
Regards,
Joe Wasilewicz
From: Simon Brooke
Subject: Re: Building Common Lisp
Date:
Message-ID: <CvIJy0.1po@exnet.com>
Does anyone know what CD-ROM GNU CL is on, where it can be obtained, and
what it costs? (I don't have a fast feed and don't fancy the phone bill
for pulling it over the wire). Has anyone compiled it on a BSD 4.3
variant? Did it go? Any problems? How much core does it need?
If anyone is interested I'll summarise back.
--
.::;====r==\ ····@uk.co.exnet (Simon Brooke)
/ /____||___\____ MS Windows IS an operating environment.
//==\ ~||~ | /__\( C++ IS an object oriented programming language.
//____\___||___|_// \|: Citroen 2cv6 IS a four door family saloon.