Hi,
The following is representative of an obscure bug I'm trying to resolve (without direct access to the computer). It affects A-B-L 0.3.8 and a recent release of ASDF, but I don't see any relevant changes to either project in the past couple years.
To set up this example, # cd /path/to/.asdf # ln -s ../asdf-binary-locations/asdf-binary-locations.asd .
Then under LispWorks on a PPC mac,
CL-USER > (push #P"/path/to/.asdf/" asdf:*central-registry*) CL-USER > (asdf:operate 'asdf:load-op :asdf-binary-locations) ; loading system definition from ; /path/to/.asdf/asdf-binary-locations.asd into ; #<The ASDF0 package, 0/16 internal, 0/16 external> ; Loading text file /path/to/.asdf/asdf-binary-locations.asd ; registering #<SYSTEM ASDF-BINARY-LOCATIONS 200B9373> as ASDF-BINARY-LOCATIONS Error: The file #P"/path/to/.asdf/dev/main.lisp" does not exist.
ASDF is clearly resolving the symlink to read A-B-L.asd; but its using the wrong path to load the source files. Is the custom load-op for load-only-cl-source-file somehow skipping the normal truename/path merging process? Any other ideas or things to look for?
Thanks, Daniel