[Openmcl-devel] Weird ASDF problem

Robert Goldman rpgoldman at sift.info
Sun Sep 12 07:01:44 PDT 2010

On 9/11/10 Sep 11 -11:47 PM, Ron Garret wrote:
> On Sep 11, 2010, at 6:48 PM, Robert Goldman wrote:
>> On 9/11/10 Sep 11 -1:53 PM, Ron Garret wrote:
>>> On Sep 11, 2010, at 11:42 AM, Ron Garret wrote:

>> Is there any reason we shouldn't replace
>> #+clozure (,(wilden (truename #p"ccl:")) ())
>> with
>> #+clozure (,(wilden (let ((*default-pathname-defaults* #P""))
>>                      (truename #p"ccl:"))) ())
>> in asdf.lisp?
> There might be someone out there who has a setting for *default-pathname-defaults* that plays nicely with (truename #p"ccl:") and whose behavior they are relying on.  This patch would break that.  Of course, there may not be any such people.  The community is not that big.

Not in this case.  This is a deeply internal aspect of ASDF 2, and it
really wants to get a directory (well wildcard, actually) pathname out.
 No one should be messing with the interpretation of "ccl:" here.

> It would help if I understood what wrapping-output-translations was supposed to do.  There's a comment on that line that says:

wrapping-output-translations is supposed to help initialize the
output-translations code which does, roughly, what
ASDF-BINARY-TRANSLATIONS used to do --- allow you to redirect the
compiled files to different locations.  This is a critical piece of
function for those of us who run more than one CL on a single box.

>  ; not needed: no precompiled ASDF system
> so maybe the whole thing is, as the comment says, not needed :-)

I don't think so --- I think this comment may date to before the time
when ASDF 2 was bundled with CCL.

More information about the Openmcl-devel mailing list