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

[Marco A. <ma...@cs...>]

Can you inspect the "foreign-interface" module and send out the result 
of a DESCRIBE?

On Aug 19, 2005, at 10:23 AM, Raymond Toy wrote:

>>>>>> "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"

This may not be all that kosher.  The source-pathname here should 
probably be "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.

I just recompiled matlisp under CMUCL and did not have any problems.  
If you have to make changes, I'd try adding the trailing #\; first.

Cheers

--
Marco Antoniotti					http://bioinformatics.nyu.edu
NYU Courant Bioinformatics Group		tel. +1 - 212 - 998 3488
715 Broadway 10th FL				fax. +1 - 212 - 998 3484
New York, NY, 10003, U.S.A.