From: Donald R Lloyd
Subject: PD Common Lisp for Amiga, PC?
Date:
Message-ID: <Btyo7E.IxH@news.udel.edu>
(Please reply via e-mail as I don't read any of these groups on a regular
basis. I'd be happy to summarize to the net if there's a demand for it).
I'm taking an AI course this semester at the U of D and, since
Common Lisp seems to be the language we'll be using, I'd like to have
a version to run on the various systems I use off-campus. Can anyone
recommend to me a Common Lisp interpreter for the Amiga (A3000, OS 2.04
compatible) or DOS machines (DOS5 in particular)?
I used Scheme a bit a few years ago. How similar is Scheme to
Common Lisp? (Forgive me for being essentially clueless about Lisp
dialects in general :-)
Thanks in advance.
--
Don Lloyd / "...my brain IBM; so if you see me acting strangely,\
···@chopin.udel.edu \ don't be surprised." - Styx, 'Mr. Roboto' /
Gibberish is Spoken Here. Publications Editor, AmigaNetwork
MicroSoft Slogan: Resistance is Futile. You Will Be Assimilated.
From: E. Malcolm Crosby
Subject: Re: PD Common Lisp for Amiga, PC?
Date:
Message-ID: <3EWCr*F12@emcamiga.UUCP>
In article <··········@news.udel.edu>, Donald R Lloyd writes:
> I'm taking an AI course this semester at the U of D and, since
> Common Lisp seems to be the language we'll be using, I'd like to have
> a version to run on the various systems I use off-campus. Can anyone
> recommend to me a Common Lisp interpreter for the Amiga (A3000, OS 2.04
> compatible) or DOS machines (DOS5 in particular)?
>
I would also like to hear about a PD version oc Common Lisp.
----
E. Malcolm Crosby
Internet: ·······@bsa1.kent.edu
E-Mail: ················@redpoll.neoucom.edu (E-Mail Please)
From: Jeff Hartung
Subject: Re: PD Common Lisp for Amiga, PC? (long)
Date:
Message-ID: <1559@cogsci.ucsd.EDU>
Hi. A few years ago I was in a LISP class and we used Kyoto Common LISP
(KCL). I checked, and the site that had the source code to KCL,
rascal.ics.utexas.edu, still has it, plus patches to bring it up to the most
recent version. Now, we had this compiled on Sun and VAX machines running
UNIX. I don't know it the code can be coerced to make on a PC or Amiga, but
the price is certaqinly right. :-)
Anyhow, here's the AKCL.README file from rascal's /pub directory:
--Jeff Hartung--
Disclaimer: My opinions only, etc., etc., BLAH! BLAH! BLAH!...
InterNet - ·······@crl.ucsd.edu BITNET - ·······@ucsd
UUCP - ucsd!crl.ucsd.edu!hartung
---------------------------------CUT HERE---------------------------------
Description of AKCL system.
OVERVIEW:
The AKCL system contains original files and change files (usually V/*
files). The change files are then combined with files in the original
KCL distribution. The latter is the June 1987 version. The utility
merge, takes files from the original distribution and modifies them
according to a prescription in a `change file'. The change files
reside in the directory V. The enhancements include enhancements to
the lisp compiler, loader, garbage collector and to the basic C code.
If installed properly NOTHING in the original kcl directory should be
overwritten. Files which have not changed will have only a link copy
in the akcl directory, and files which do change will have a changed
copy in the akcl directory, and an unchanged file in the kcl
directory. To ensure that you do not accidentally alter a file in the
original directory you might wish to make the files there unwritable.
You do not need to do a make in the kcl directory.
OBTAINING SOURCES:
-----------------
* There are source files on rascal.ics.utexas.edu:pub/akcl-XX.tar.Z
You probably want the highest XX version number. For example
akcl-1-605.tar.Z would allow you to build the version 1-605 of AKCL. In
the following this compressed tar file is simply referred to as
akcl.tar.Z. You will also need to obtain the original kcl distribution
of June 1987. That is referred to as kcl.tar.Z and is also available
on rascal. An alternate source for these files is cli.com:akcl/akcl-XX.tar.Z
In general the bandwidth to rascal is higher than to cli.com.
Rascal's address is rascal.ics.utexas.edu (128.83.138.20).
* If you cannot obtain these files via internet, a cartridge tape (sun
compatible) or diskettes containing akcl, and kcl sources may be
obtained for $250 US plus shipping, from J. Schelter, 1715
Barnswallow, Autin TX 78746. This would be in standard tar format.
Some machines on which akcl compiles are 386 under System V (eg
Microport), Sun's (sparc,sun3's), HP under hpux and 4.3, Dec mips ultrix,
Sgi mips irix.
MAKING THE SYSTEM:
==================
To make the whole system, if you have obtained akcl.tar.Z and
kcl.tar.Z
UNCOMPRESS and UNTAR the SOURCES:
--------------------------------
Change to a directory in which you wish to put the kcl and akcl
subdirectories. Make sure the two files kcl.tar.Z and akcl.tar.Z are
in your current directory. When you extract the files make sure the write
file write dates are as in the distribution--make needs this.
% mkdir kcl
% (cd kcl ; uncompress -c ../kcl.tar.Z | tar xvf -)
% mkdir akcl
% cd akcl
% uncompress -c ../akcl.tar.Z | tar xvf -
ADD MACHINE DEFINITIONS TO MAKEFILES:
------------------------------------
Determine the NAME of your machine by looking in the MACHINES file (eg
sun3-os4). Also remember where you untarred kcl.tar.Z (eg
/public/kcl)
% add-defs sun3-os4 /public/kcl
(in general % add-defs NAME DIRECTORY-WHERE-KCL-IS)
You should finally be ready to go!
RUNNING MAKE:
------------
% make -f Smakefile
NOTE: Smakefile is a special makefile which causes make to be run
twice, the first time building a saved_kcl using some interpreted
code, and the second time compiling itself. If this does not run
twice you will be using a good deal of interpreted code as well as a
combination of old and new compiler, which while sufficient to compile
the new compiler, would not be good for general use. If you later
change files it will be sufficient to just use the regular makefile
(which has by now been slightly altered).
The make should continue without error. There may be occasional
warnings from the C compiler, but all files should compile successfully
producing .o files.
The V/* change files will only be used if they are newer (normally the
case) than the existing files. If you have modified files in the akcl
directory, eg. c/array.c, but wish merge to overwrite that with its
merged version, you could for example % touch V/c/array.c. Building
akcl successfuly through the second pass, will mail a version info
message to akcl so we know which cpu, c compiler and os levels are
working properly, as well as printing out a message "Make of AKCL xxx
completed", where xxx stands for the version number.
When it has finally finished you may invoke AKCL by using
TRY IT OUT:
----------
% xbin/kcl
AKCL (Austin Kyoto Common Lisp) Version(1.65) Wed Sep 21 00:52:31 CDT 1988
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).
ELIMINATE SOME FILES?
--------------------
What to keep if you have no space! The only files which are ESSENTIAL
to running of AKCL COMMON LISP once you have built the system (if you are
using sfasl, as is default on a sun eg).
unixport/saved_kcl
/usr/local/bin/akcl (copy of xbin/akcl)
Also if you are able to use sfasl, you may even % strip saved_kcl.
Of course keeping sources, documentation, etc. is desirable.
doc/DOC
doc/DOC-keys.el
And there are a few unloaded files */*.lisp which are useful to keep.
For example lsp/make.lisp.
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 "/public/akcl/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.
INSTALL:
=======
After the system has been built, in the main akcl directory
% make install
will copy the command to execute kcl to the LBINDIR,
and will also attempt to install the documentation interface
for gnu emacs. You will have to have write permission in the
emacs directory, and LBINDIR for this, so you may need to
be super user.
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?
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$(AKCLDIR)/o
Or, if you are using the conventional UNIX C compiler:
CC = cc -DVOL= -I. -I$(AKCLDIR)/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.
---------------------------------CUT HERE---------------------------------
--
--Jeff Hartung--
Disclaimer: My opinions only, etc., etc., BLAH! BLAH! BLAH!...
InterNet - ·······@crl.ucsd.edu BITNET - ·······@ucsd
UUCP - ucsd!crl.ucsd.edu!hartung
In article <·········@emcamiga.UUCP> ················@redpoll.neoucom.edu writes:
>I would also like to hear about a PD version oc Common Lisp.
I replied to the original posting by mail rather than following up, because
I've adopted a policy of not posting responses that are already answered in
the FAQ. That's the whole point of the FAQ, isn't it? I'm posting this
message hopefully to stop the apparent flurry of responses.
The Lisp/Scheme/CLOS FAQ may be FTPed from ftp.think.com, in the file
/public/think/lisp/faq.text. Information about available Lisp
implementations is in section [4-0].
--
Barry Margolin
System Manager, Thinking Machines Corp.
······@think.com {uunet,harvard}!think!barmar