[asdf-devel] possible clisp/win32 incompatibility

[dherring at tentpost.com]

Robert Goldman wrote:
> On 1/24/10 Jan 24 -3:01 PM, Daniel Herring wrote:
>> Thanks for the ideas.  Poking around a bit further, it appears that in
>> the following snippet from output-files-using-mappings
>> (*centralize-lisp-binaries* is false), (pathname-directory path) is nil.
>>
>>                  (make-pathname
>>                   :type (pathname-type path)
>>                   :directory (append
>>                               (pathname-directory path)
>>                               (implementation-specific-directory-name))
>>                   :defaults path)))))
>>
>> Thus clisp is seeing ":directory (clisp)" without a leading :relative or
>> :absolute.  I don't know the cause and am focused on other issues right
>> now (this one has a couple workarounds: use ccl or an older asdf).
>
> Can you trace pathname-type inside the invocation of
> output-files-using-mappings?  This smells like a CLISP bug to me....

Here's some relevant FORMAT ~S output.  "p:" is the full path right before
the error; p-d is the pathname-directory.

;; Loaded file #<INPUT BUFFERED FILE-STREAM CHARACTER C:\Documents and
Settings\nuntius\Desktop\able-release\systems\ltk\ltk.asd @19>
p: #P"C:ltk.fas"
p-d: NIL
*** - MAKE-PATHNAME: Illegal :DIRECTORY argument ("clisp-2.48-win32-i386")

Something bad happened before this call; the paths list is screwed up in
the output-files defmethod around compile-op (a few lines below the above
snippet).  It is merely (#P"C:ltk.fas").

>From a few TRACEs, it appears that *default-pathname-defaults* is #P"C:",
and this is the value of component-parent-pathname. 
Component-relative-pathname is "ltk.lisp".

- Daniel