Re: [Matlisp-users] mk::defsystem problem? Allegro 7.0 trial/MacOSX 10.4

[Raymond T. <ray...@er...>]

>>>>> "Marco" == Marco Antoniotti <ma...@cs...> writes:

    Marco> Hi

    Marco> This looks more like a Logical Pathname problem with ACL 7.0.

Could be, but could be defsystem too.  I've always had some problems
with logical pathnames and defsystem.

    Harri> ;    - Loading module "foreign-interface"
    Harri> Warning: An error occurred
    Harri>           (No translation rule for #P"matlisp:;src;f77-mangling.lisp")
    Harri>           during the reading or evaluation of -e

Is rather suspicious because the defsystem there says 

(mk::defsystem matlisp
      :source-pathname "matlisp:"
      :source-extension "lisp"
      :binary-pathname "matlisp:bin;"
      :depends-on ("lazy-loader"
                   "matlisp-packages")
      :components
      ((:module "foreign-interface"
	:source-pathname "matlisp:src"
	:source-extension "lisp"
	:binary-pathname ""
	:components ("f77-mangling"
		     #+:cmu "ffi-cmu"
		     #+:sbcl "ffi-sbcl"
		     #+:allegro "ffi-acl"
		     ))
       ...))


I don't see how it could produce the pathname
"matlisp:;src;f77-mangling.lisp".  It should be
"matlisp:src;f77-mangling.lisp".


As a workaround, Harri could just change "matlisp:src" to be
(translate-logical-pathname "matlisp:src") and similarly in other
places.

Ray