[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Problem compiling Victoria Day PCL
- To: hall@aic.nrl.navy.mil, barford@hpllab.hp.com
- Subject: Problem compiling Victoria Day PCL
- From: Jon L White <jonl@lucid.com>
- Date: Wed, 5 Jul 89 22:02:21 PDT
- Cc: commonloops.pa@Xerox.COM
- In-reply-to: Lawrence Hall's message of Tue, 20 Jun 89 14:01:16 EDT <8906201801.AA22933@aic.nrl.navy.mil>
- Redistributed: commonloops.pa
Hmmm, I quite frankly don't see how any of the PCL in recent times could
work in a Lucid Lisp of the vintage you have -- Sun 2.1.1. My copy of
that release here doesn't even have the symbol
LUCID::AUGMENT-LEXENV-FVARS-DUMMY
in it. However, I do notice patched-up definition of it in walk.lisp
as follows:
#+Prime
(defun lucid::augment-lexenv-fvars-dummy (lexical vars)
(lucid::augment-lexenv-fvars-aux lexical vars '() '() 'flet '()))
Perhaps that #+Prime should be extended to cover this case as well. A
first cut would be #+(or Prime (and mc68000 sun (not lcl3.0)))
The problem solved by the reply from barford@hpllab.hp.com is, I think,
a different one. Gregor: current release has one place in defs.lisp
and one in boot.lisp where the token
lucid-common-lisp:*redefinition-action*
occurs [one place uses two colons]. Sad to say, if you don't import
this symbol into the PCL package, it will have to be qualified
differently depending on whether it is the 2.1 or 3.0 release. I
would approve of yet another resort to the kludge of doing it as
lucid::*redefinition-action*
in these two instances.
-- JonL --