[Ecls-list] Order of requiring cmp and asdf

Juan Jose Garcia-Ripoll juanjose.garciaripoll at googlemail.com
Sun Jun 26 19:58:13 UTC 2011


On Thu, Jun 23, 2011 at 3:58 PM, Marko Kocić <marko.kocic at gmail.com> wrote:

> Why requiring asdf and then cmp fails, while requiring cmp and asdf works?
>

This only happens in windows, where the bytecmp module (bytecodes compiler)
is loaded by default. The problem is the following one.

Path 1: bytecmp -> cmp -> asdf

This works, as CMP redefines COMPILE-FILE-PATHNAME and ASDF may work with
the new compiler (which replaces the bytecodes compiler without problems).

Path 2: bytecmp -> asdf -> cmp

This does not work. ASDF overwrites REQUIRE and relies on
COMPILE-FILE-PATHNAME, which tells ECL that the name of a compiled file
called CMP has to be cmp.fasc (vs. cmp.fas which is the real name).

I do not see a simple escape out of this, other than creating ficticious
*.fasc files for every *.fas file in ECL's library.

Juanjo

-- 
Instituto de Física Fundamental, CSIC
c/ Serrano, 113b, Madrid 28006 (Spain)
http://juanjose.garciaripoll.googlepages.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.common-lisp.net/pipermail/ecl-devel/attachments/20110626/aa01cac7/attachment.html>


More information about the ecl-devel mailing list