[asdf-devel] Q about ASDF on LW

[Robert Goldman]

On 1/20/10 Jan 20 -1:59 PM, Nick Levine wrote:
>    From: =?ISO-8859-1?Q?Far=E9?= <fahree at gmail.com>
>    Date: Wed, 20 Jan 2010 14:30:48 -0500
>    Cc: Nick Levine <ndl at ravenbrook.com>, asdf-devel at common-lisp.net
> 
>    If you actually send the backtrace on the list, or attach it to an
>    ASDF bug on launchpad.net, that would help a lot figure out what's
>    wrong and how to fix it.
> 
> Here it is. Note that the "extend stack by 50%" restart did the trick.
> 
> - nick
> 
> 
> 
> CL-USER 1 > (lisp-implementation-version)
> "5.1.2"
> 
> CL-USER 2 > (load #P"c:/tmp/downloads/libcl-2010-01-18-snapshot/asdf/asdf.lisp")
> ; Loading text file c:\tmp\downloads\libcl-2010-01-18-snapshot\asdf\asdf.lisp
> #P"c:/tmp/downloads/libcl-2010-01-18-snapshot/asdf/asdf.lisp"
> 
> CL-USER 3 > (pushnew #P"c:/tmp/downloads/libcl-2010-01-18-snapshot/_asdf/" asdf:*central-registry* :test #'equal)
> (#P"c:/tmp/downloads/libcl-2010-01-18-snapshot/_asdf/" (DIRECTORY-NAMESTRING *DEFAULT-PATHNAME-DEFAULTS*))
> 
> CL-USER 4 > (asdf:operate 'asdf:load-op :asdf-binary-locations)

The latest version of ASDF integrates the functionality of
asdf-binary-locations, so it's probably a Bad Thing to try to load A-B-L
on asdf2.

I'm actually somewhat tempted to hack a special purpose check in to
treat this as an error in ASDF2.

Best,
r