[asdf-devel] never ending component relative pathnames

[Faré]

I darcs pull'ed from http://common-lisp.net/~crhodes/clx which
compiled fine with ASDF 1.627. clx.asd says it's 0.7.2, NEWS says it's
0.7.3, and stassats says it's 0.7.4 (after using diff to confirm).

In any case, I don't have any problem with (:relative) at least, not under SBCL.
Do you have a backtrace of the error?

Are you using logical pathnames? Maybe I should disable the output
translation layer when using logical pathnames?

[ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ]
Those who are afraid to take the next step will have wasted their entire
previous journey. — Baron von Richthofen


On 5 March 2010 13:06, james anderson <james.anderson at setf.de> wrote:
> good evening;
>
> on the occasion of pushing de.setf.graphics down the wire, when i
> built it for ccl/sbcl i did an obligatory pull on asdf and observe
> that something changed in the treatment of modules' component
> relative pathnames. with the effect that it was no longer possible
> possible to build clx. the clx-0-7-4 version as (:relative)
> specification in module pathnames which ran afoul of the asdf
> changes. i applied the same tactic as i have previously found
> effective for source file components and was able to build. the diff
> [1] is posted with the graphics sources.
>
> on other semi-related matters, i can report, that i have now an s3
> ami (linux-2.6.31+ubuntu++^3) with which i can boot an ec2 instance
> with all pieces in place to run the target lisp implementations.
>
>
> ---
>  [1] : http://github.com/lisp/de.setf.graphics/blob/master/readmes/
> asdf.diff
>
>
> _______________________________________________
> asdf-devel mailing list
> asdf-devel at common-lisp.net
> http://common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel
>