[asdf-devel] ASDF breaks ECL's use of :PATHNAME

Faré fahree at gmail.com
Sat Oct 27 23:51:09 UTC 2012


> I did not mean that it touches the relative pathname, but the fact is that
> ASDF does not use the path which is passed. Instead, at various parts, this
> path is translated into an absolute path and that involves changing the type
> of the relative path.
>
Can you give a reproducible example?

> As I said, something must have changed w.r.t. to relatives paths between
> asdf(old)+asdf-ecl  and asdf(new)+asdf-bundle, because the lines below used
> to work
>
> (ext::install-bytecodes-compiler)
> (setf *load-verbose* t)
> (require :asdf)
> (load "~/quicklisp/setup")
>
This particular example looks like it works for me on
ecl-12.7.1-52ca46e0-linux-x64.
So does replacing the (require :asdf) by loading 2.25.4. On the other hand,
(asdf:upgrade-asdf) from the builtin 2.017.5 miserably segfaults :-(

—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org
Truth is stranger than fiction, but it is because Fiction is obliged to
stick to possibilities. Truth isn't. — Mark Twain




More information about the asdf-devel mailing list