Previous: How can I wholly disable the compiler output cache?, Up: Issues with configuring ASDF [Contents][Index]
Sometimes ASDF will be unable to find and load your systems, although you believe that it should be able to. There are a number of things you can do to debug such issues.
If you are using asdf:*central-registry*
(see ASDFがシステムを見つけられるように設定する(古いスタイル)),
you can
simply look at the pathnames and namestrings in this variable, and use
conventional tools such as cl:probe-file
and cl:directory
to poke around and see why your systems are not being found.
If you are using one of the newer methods for configuring ASDF’s system finding (see ASDFがシステムを探す場所を設定する), you can try:
(alexandria:hash-table-alist asdf/source-registry::*source-registry*)
(alphabetizing the results here may be helpful). Or for a higher-level view:
(asdf/source-registry:flatten-source-registry)
Finally, if you use the source registry cache (see ソースレジストリのキャッシュ), you can:
find ~/common-lisp -name .cl-source-registry.cache
at the shell.
It is still, unfortunately, an open question how to monitor ASDF’s interpretation of its source configuration as it happens.