[asdf-devel] Issues with logical pathnames in Allegro and clisp

Pascal Costanza pc at p-cos.net
Sun Jan 23 14:27:37 UTC 2011


I have encountered two more issues when trying to use ASDF 2 with logical pathnames in Allegro and clisp. I have the following logical pathname translations in Allegro and clisp respectively:

(setf (logical-pathname-translations "costanza")
      `(("**;*.fasl.*" ,(format nil "/Users/costanza/.cache/common-lisp/~A ~A/**/*.fasl"
                                (read-from-string (lisp-implementation-version))))
        ("**;*.*.*" "/Users/costanza/**/*.*")))

  (setq custom:*parse-namestring-ansi* t)

  (setf (logical-pathname-translations "costanza")
        `(("**;*.lib.*" ,(format nil "/Users/costanza/.cache/common-lisp/~A ~A/**/*.lib"
                                 (read-from-string (lisp-implementation-version))))
          ("**;*.fas.*" ,(format nil "/Users/costanza/.cache/common-lisp/~A ~A/**/*.fas"
                                 (read-from-string (lisp-implementation-version))))        
          ("**;*.*.*" "/Users/costanza/**/*.*"))))

When compiling systems with ASDF, however, the fasl, lib and fas files don't end up in the folders designated by these logical pathname translations, but rather in the locations as specified with ASDF output translations. (In CMUCL, Clozure, ECL, LispWorks, RMCL, and SBCL, similar logical pathname translations work as expected.)

I have not defined any ASDF output translations of my own, but I'm using quicklisp, which probably does this.

Please let me know if I can do something to help fixing this problem.


Pascal Costanza, mailto:pc at p-cos.net, http://p-cos.net
Vrije Universiteit Brussel
Software Languages Lab
Pleinlaan 2, B-1050 Brussel, Belgium

More information about the asdf-devel mailing list