From bancroft@snowball.ucdavis.edu  Fri May 11 12:51:16 1990
Received: by iris.ucdavis.edu (5.57/UCD.EECS.2.0)
        id AA15855; Fri, 11 May 90 12:51:16 PDT
Received: from snowball.ucdavis.edu by clover.ucdavis.edu (5.59/UCD.EECS.1.11)
        id AA12395; Thu, 10 May 90 16:28:30 PDT
Received: by snowball.ucdavis.edu (4.0/3.14)
        id AA12135; Thu, 10 May 90 16:24:28 PDT
Date: Thu, 10 May 90 16:24:28 PDT
From: bancroft@snowball.ucdavis.edu (Steven Bancroft)
Message-Id: <9005102324.AA12135@snowball.ucdavis.edu>
To: info-hol@clover
Subject: HOL build prob. w/ SUN CL 3.0.4

I am attempting to build the HOL system using Sun Common Lisp 3.0.4 on
a Sun3-OS4 machine.  All of the lisp code in the lisp/ directory
compiles fine, but then when it tries to start compiling the ml code,
I get problems.  Here is what happens:

[ normal compilation for the HOL system lisp code, then... ]

echo '(load "lisp/mk-ml")'\
     '(load "lisp/mk-hol-lcf")'\
     '(setq %system-name "HOL-LCF")'\
     '(setq %liszt "$(LisztComm)")'\
     '(setq %version "$(Version)")'\
     '(set-make)'\
     '(tml)'\
     'compile(`ml/ml-curry`,true);;'\
     'quit();;'\
     | /usr/lisp/lisp

;;; Enabling ephemeral garbage collection.
;;;
;;; Sun Common Lisp, Development Environment 3.0.4, 2 August 1988
;;; Sun-3 Version for SunOS 4.0

[ other intro stuff ]

>
;;; Loading binary file "lisp/mk-ml.lbin"
;;; Loading binary file "lisp/f-cl.lbin"

[ all the other successful binary loads ]
[ starts to parse the ml code in ml/ml-curry ]

compiling_stack = [] : bool list

load = - : ((string # bool) -> void)

compile = - : ((string # bool) -> void)

Calling Lisp compiler
error --
evaluation failed      compile -- Lisp compilation failed
*** Error code 1
make: Fatal error: Command failed for target `ml/ml-curry_ml.o'

----------

For some reason, the HOL code isn't able to find the lisp compiler.
I have tried building the system with both the production and
development modes of the Sun CL package, each producing the same
results.

Note: It is known that HOL has been successfully built using
Sun Common Lisp (Lucid) 2.1.1.

Is there something I can do to fix this problem?

Thanks,

Steven Bancroft
University of California, Davis
bancroft@iris.ucdavis.edu

