Hi,
I just installed CMUCL 20e on my Mac OS X 10.8.5. CMUCL 20e release notes say that it comes with ASDF 3.0.2.
My .cmucl-init.lisp file looks like this:
(setf (logical-pathname-translations "costanza") `(("**;*.fasl.*" ,(format nil "/Users/costanza/.cache/common-lisp/~A ~A/**/*.fasl" (lisp-implementation-type) (lisp-implementation-version))) ("**;*.*.*" "/Users/costanza/**/*.*")))
;;; The following lines added by ql:add-to-init-file: #-quicklisp (let ((quicklisp-init (merge-pathnames "quicklisp/setup.lisp" (user-homedir-pathname)))) (when (probe-file quicklisp-init) (load quicklisp-init)))
When I start CMUCL, I see this:
; Loading #P"/Users/costanza/.cmucl-init.lisp". ;; Loading #P"/Users/costanza/quicklisp/setup.lisp". ;;; Loading #P"/Users/costanza/lib/cmucl/lib/contrib/asdf/asdf.sse2f".
Error in function UIOP/UTILITY:CALL-FUNCTION: Invalid pathname #P"~/lisp/develop/": Expected an absolute pathname [Condition of type SIMPLE-ERROR]
Restarts: 0: [REINITIALIZE-SOURCE-REGISTRY-AND-RETRY] Retry finding system asdf after reinitializing the source-registry. 1: [CONTINUE ] Return NIL from load of #P"home:quicklisp/setup.lisp". 2: Return NIL from load of "home:.cmucl-init". 3: [ABORT ] Skip remaining initializations.
Debug (type H for help)
(UIOP/UTILITY:CALL-FUNCTION ERROR "Invalid pathname ~S: ~*~?" #P"~/lisp/develop/" :WANT-ABSOLUTE ...) Source: ; File: modules:asdf/asdf.lisp
; File has been modified since compilation: ; modules:asdf/asdf.lisp ; Using form offset instead of character position. (APPLY (ENSURE-FUNCTION FUNCTION-SPEC) ARGUMENTS) 0]
What do I do?
Pascal
-- Pascal Costanza The views expressed in this email are my own, and not those of my employer.
OK, found it. Apparently, you cannot use "~" in ASDF configurations anymore. Sigh…
Pascal
On 5 Oct 2013, at 12:30, Pascal Costanza pc@p-cos.net wrote:
Hi,
I just installed CMUCL 20e on my Mac OS X 10.8.5. CMUCL 20e release notes say that it comes with ASDF 3.0.2.
My .cmucl-init.lisp file looks like this:
(setf (logical-pathname-translations "costanza") `(("**;*.fasl.*" ,(format nil "/Users/costanza/.cache/common-lisp/~A ~A/**/*.fasl" (lisp-implementation-type) (lisp-implementation-version))) ("**;*.*.*" "/Users/costanza/**/*.*")))
;;; The following lines added by ql:add-to-init-file: #-quicklisp (let ((quicklisp-init (merge-pathnames "quicklisp/setup.lisp" (user-homedir-pathname)))) (when (probe-file quicklisp-init) (load quicklisp-init)))
When I start CMUCL, I see this:
; Loading #P"/Users/costanza/.cmucl-init.lisp". ;; Loading #P"/Users/costanza/quicklisp/setup.lisp". ;;; Loading #P"/Users/costanza/lib/cmucl/lib/contrib/asdf/asdf.sse2f".
Error in function UIOP/UTILITY:CALL-FUNCTION: Invalid pathname #P"~/lisp/develop/": Expected an absolute pathname [Condition of type SIMPLE-ERROR]
Restarts: 0: [REINITIALIZE-SOURCE-REGISTRY-AND-RETRY] Retry finding system asdf after reinitializing the source-registry. 1: [CONTINUE ] Return NIL from load of #P"home:quicklisp/setup.lisp". 2: Return NIL from load of "home:.cmucl-init". 3: [ABORT ] Skip remaining initializations.
Debug (type H for help)
(UIOP/UTILITY:CALL-FUNCTION ERROR "Invalid pathname ~S: ~*~?" #P"~/lisp/develop/" :WANT-ABSOLUTE ...) Source: ; File: modules:asdf/asdf.lisp
; File has been modified since compilation: ; modules:asdf/asdf.lisp ; Using form offset instead of character position. (APPLY (ENSURE-FUNCTION FUNCTION-SPEC) ARGUMENTS) 0]
What do I do?
Pascal
-- Pascal Costanza The views expressed in this email are my own, and not those of my employer.
-- Pascal Costanza The views expressed in this email are my own, and not those of my employer.
Pascal Costanza pc@p-cos.net writes:
OK, found it. Apparently, you cannot use "~" in ASDF configurations anymore.
~ syntax has never worked in CMUCL pathnames before. Did it start working in 20e?
Zach
On 5 Oct 2013, at 15:41, Zach Beane xach@xach.com wrote:
Pascal Costanza pc@p-cos.net writes:
OK, found it. Apparently, you cannot use "~" in ASDF configurations anymore.
~ syntax has never worked in CMUCL pathnames before. Did it start working in 20e?
I guess not. I test Closer to MOP on CMUCL only on major releases, and since CMUCL 20d, I had to change my ASDF configuration a couple of times. Apparently, I chose something that doesn't work on CMUCL. Anyway, it works now when supplying the full pathname.
Pascal
-- Pascal Costanza The views expressed in this email are my own, and not those of my employer.
Dear Pascal,
while we're at it, since you are one of the few users of "logical" pathnames in the world, your feedback is most welcome as to what does or doesn't work in such a setting. There are now tests for logical pathnames in ASDF, but I doubt they cover all the cases, so there may be "interesting" failures despite all our best efforts.
—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org Few facts are more revealing than the direction people travel when they vote with their feet. — Don Boudreaux http://bit.ly/afZgx2
On Sat, Oct 5, 2013 at 12:05 PM, Pascal Costanza pc@p-cos.net wrote:
On 5 Oct 2013, at 15:41, Zach Beane xach@xach.com wrote:
Pascal Costanza pc@p-cos.net writes:
OK, found it. Apparently, you cannot use "~" in ASDF configurations anymore.
~ syntax has never worked in CMUCL pathnames before. Did it start working in 20e?
I guess not. I test Closer to MOP on CMUCL only on major releases, and since CMUCL 20d, I had to change my ASDF configuration a couple of times. Apparently, I chose something that doesn't work on CMUCL. Anyway, it works now when supplying the full pathname.
Pascal
-- Pascal Costanza The views expressed in this email are my own, and not those of my employer.
-
Faré -
Pascal Costanza -
Zach Beane