[asdf-devel] Recompiling SBCL contribs

[Zach Beane]

Faré <fahree at gmail.com> writes:

> I recompiled an SBCL 1.1.9, which is close to your 1.1.8.30 and just
> before it upgraded to ASDF 3.0.2, and couldn't reproduce your issue;
> can you give me steps to reproduce, if possible minimal?
>
> Also, is your sbcl install the fruit of a cp -r without timestamp
> preservation? Are there clock skew issues between your host and e.g.
> an NFS server?
>
> In your TRAVERSE output, what we're looking for is the first
> compilation of a lisp file. It's also possible that some static-file
> with a high timestamp cause the next system over to think it must be
> recompiled.

I'll try to put together a small test case. In the meantime, here are my
ultimate goals:

  - Load internal (e.g. "ASDF") and special (e.g. SBCL contribs) systems
    normally

  - Strictly and explicitly map where all other systems are found, with
    no fallback to the central registry, source registry, etc.

  - Save all FASLs for non-internal, non-special systems in a fresh
    directory of my choosing

The idea is to isolate the system load and avoid introducing untracked
implicit dependencies from outside sources.

Zach