The presense of the :COMPONENTS field produces the error:
Type-error in KERNEL::OBJECT-NOT-TYPE-ERROR-HANDLER:
#() is not of type (OR CONS BASE-STRING (MEMBER NIL :UNSPECIFIC :WILD) COMMON-LISP::PATTERN)
The LISP system in use is:
lisp
CMU Common Lisp 18c, Built 2000-11-27, running on skeletal
Send questions and bug reports to your local CMU CL maintainer, or to cmucl-help@cons.org. and cmucl-imp@cons.org. respectively.
Loaded subsystems:
Python 1.0, target SPARCstation/Solaris 2
CLOS based on PCL version: September 16 92 PCL (f)
CLX X Library MIT R5.02
Motif toolkit and graphical debugger 1.0
Hemlock 3.5
*
and MATLISP 1.0b
any help here?
tnx
mike
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You are right. I think this is a bug in the defsystem included with matlisp.
I'll update this with the latest version in clocc.
In the mean time you can grab the latest defsystem from clocc (on sourceforge). I know this version works because I've been using this version to build matlisp.
Ray
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm trying to build the MATLISP core under SunOS 5.7, sun4u sparc, SUNW,Ultra-4. In execution of:
(mk::defsystem lazy-loader
:source-pathname "matlisp:lib;"
:source-extension "lisp"
:binary-pathname "matlisp:bin;"
:components
((:file "lazy-loader"
:load-only t)))
The presense of the :COMPONENTS field produces the error:
Type-error in KERNEL::OBJECT-NOT-TYPE-ERROR-HANDLER:
#() is not of type (OR CONS BASE-STRING (MEMBER NIL :UNSPECIFIC :WILD) COMMON-LISP::PATTERN)
The LISP system in use is:
lisp
CMU Common Lisp 18c, Built 2000-11-27, running on skeletal
Send questions and bug reports to your local CMU CL maintainer, or to cmucl-help@cons.org. and cmucl-imp@cons.org. respectively.
Loaded subsystems:
Python 1.0, target SPARCstation/Solaris 2
CLOS based on PCL version: September 16 92 PCL (f)
CLX X Library MIT R5.02
Motif toolkit and graphical debugger 1.0
Hemlock 3.5
*
and MATLISP 1.0b
any help here?
tnx
mike
You are right. I think this is a bug in the defsystem included with matlisp.
I'll update this with the latest version in clocc.
In the mean time you can grab the latest defsystem from clocc (on sourceforge). I know this version works because I've been using this version to build matlisp.
Ray