1 files changed, 45 insertions, 0 deletions
diff --git a/com/cmu/README b/com/cmu/README
new file mode 100644
index 0000000..3653d60
--- /dev/null
+++ b/com/cmu/README
@@ -0,0 +1,45 @@
+This directory contains command scripts used for building Yale Haskell
+from the source distribution under CMU Common Lisp on the sparc.
+
+We have been using version 16f of CMU Common Lisp to build Haskell.
+You can ftp this from lisp-rt1.slisp.cs.cmu.edu (128.2.217.9).
+There is a known problem with this version of CMU CL: core files built
+under SunOS 4.1.2 won't work under 4.1.3, and vice versa.  There are
+also apparently compatibility problems with 4.1.3 between sun4c and
+sun4m architectures.  Anyway, we have built under 4.1.2 on a sun4c
+and 4.1.3 on a sun4m.
+
+Developers need to source haskell-development instead of haskell-setup
+in the .cshrc file.
+
+To rebuild the system:
+
+* You need to define environment variables Y2, CMUCL, and CMUCLLIB to 
+  point to the appropriate pathnames.  See the haskell-development 
+  script for details.
+
+* Make sure that the environment variable PRELUDEBIN (in the 
+  haskell-setup script) points to $PRELUDE/cmu.
+
+* Execute the "compile" script.  This will recompile all of the Lisp 
+  source files that make up the Yale Haskell system.  Compiled files
+  are put in the "cmu" subdirectory of each source directory.
+
+* Execute the "build-prelude" script to compile the standard prelude.  
+  Note that this process tends to use up a huge amount of memory!
+
+* Execute the "savesys" script to save a core file.
+
+* The new core file is initially called "bin/new-cmu-haskell.core".
+  Use the -core command line argument to cmucl to test it.  If it
+  works, you should rename it to "bin/sun4c-haskell.core" (or
+  "bin/sun4m-haskell.core") and use the "bin/cmu-haskell" script 
+  to execute it.  Make sure HASKELLPROG (in the haskell-setup script) 
+  is correct.  Depending on where you have cmucl this script may need 
+  editing.
+
+* If you want to build an executable with the X support, you'll also
+  need to run the "build-xlib" and "savesys-xlib" scripts.  You
+  need to edit these scripts to change the pathname of the file 
+  containing the CLX library (or suppress the load entirely if you
+  are using a Lisp executable with CLX pre-loaded.).