On Sun, Oct 28, 2012 at 6:41 AM, Juan Jose Garcia-Ripoll juanjose.garciaripoll@gmail.com wrote:
Currently, ASDF ignores all file types supplied by the user when specifying a :PATHNAME value for a component. This did not happen before, though.
No, it doesn't. If you pass a #p"..." pathname, then whatever you specify is used untouched. If you pass a string, then the declared type (if any) is used with it.
This behavior has worked for ever with ASDF 2. (ASDF 1 wasn't behaving portably in the corner cases.)
This is kind of annoying and hard to deal with, due to ECL's need of prebuilt ASDF files -- these are ASDF components that contain files with precompile sources, whose file extension need not coincide with the one being used by ASDF at the time.
For instance, ECL may be launched with the bytecodes compiler as default (file extension is ".fasc"), but require to load sockets.asd, which contains the precompiled binary file sockets.fas, as in
(DEFSYSTEM "sockets" :CLASS ASDF::PREBUILT-SYSTEM :LIB #P"SYS:LIBSOCKETS.A" :DEPENDS-ON NIL :COMPONENTS ((:COMPILED-FILE "sockets" :PATHNAME #P"SYS:SOCKETS.FAS")))
What would be the appropriate fix for this?
Can you give me a script that reproduces the failure?
—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org ``gode'' in French (pronounce as ``god'' in English) means a dildo; the latin word for god is ``deus'', which pronounces like the tennis scoring term ``deuce'' in English. How can anyone see anything intrinsically holy in words? — Faré