On Mon, Oct 11, 2010 at 12:12 PM, Zach Beane xach@xach.com wrote:
Lou Vanek lou.vanek@gmail.com writes:
FASL compatibility isn't required by me -- I just assumed that since I had properly set up SBCL to automatically recompile stale fasls that I had done the same for clozure, which I just figured out I did not. My bad.
The problem is not "stale" fasls in the normal sense of a fasl format change. The problem is that the package structure of ASDF changed from minor version to minor version, so fasls that reference one minor version's packages might contain invalid package references if you upgrade to a new minor version.
If you attempt a recompile on any error, rather than just the invalid fasl error, you might be able to automatically get around this problem.
Zach
You're, of course, correct, since this later version of clozure happily loaded the older fasl/lx32fsl. So my new asdf :around method that automatically recompiles stale fasls would not have fixed the asdf-utilities issue.
Lou Vanek