Bug in use of function for output translations
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ASDF |
Fix Released
|
Medium
|
Faré |
Bug Description
Jason Miller reports:
I reduced a testcase from the metacopy-
defines an output-files method to rename the .fasl so that it can
compile the same lisp files with different features set.
This worked fine when I was using normal output translations, but when I
switched to a :function output translation, it failed. I'm not sure if
this is a bug in asdf, a bug in my output translation function or a bug
in metacopy, so I'm posting it here for some advice.
Test-case is in a tarball below. There is a shell script "test.sh"
which invokes sbcl twice. The first time the output translation is left
unaltered, the second time it specifies a :function translator for all
paths, and this causes an error.
Interestingly, if you display (output-files :compile-op '("my-system" "foo")) before and after you (load-system "my-system") you find that it disagrees.
The problem is due to some recent change I did (I'm not sure which) that is causing asdf to think it's not up to date, to actually reload itself, which loses the :around method.