[asdf-devel] the same (asdf::implementation-identifier) for byte-compiler and lisp-to-C-compiler of ECL

[Anton Vodonosov]

15.01.2012, 22:46, "Faré" <fahree at gmail.com>:
> On Sun, Jan 15, 2012 at 03:54, Anton Vodonosov <avodonosov at yandex.ru> wrote:
>
>>  ECL offers two compiles: byte-compiler and lisp-to-C compiler.
>>
>>  They produce incompatible .fasls
>
> At least in a recent ECL (I tested with a git checkout from November
> 2011), they also should be using different extensions, .fas for the
> usual compiler, and .fasc for the bytecode compiler. Is there somehow
> a clash on windows because these share the same first three
> characters?

It' my mistake. I just misinterpreted other failure, and when noticed the 
implementation-identifier is the same decided (mistakenly) 
it is the cause.

Sorry for disturbing you.

>>  (in my case C:\Users\anton\AppData\Roaming\common-lisp\cache\ecl-11.1.1-win-x86\).
>
> I'm a bit surprised that LOCALAPPDATA includes Roaming\ instead of
> Local\ but then again I don't understand Windows paths very well. If
> you think that's wrong, please suggest a better heuristic for choosing
> a path to the cache.

For me Roaming is OK.

Best regards,
- Anton