Next: Issues with upgrading ASDF, Previous: Upgrading ASDF, Up: Upgrading ASDF [Contents][Index]
Most implementations provide a recent ASDF 3 in their latest release. If yours doesn’t, we recommend upgrading your implementation. If the latest version of your implementation still doesn’t provide ASDF, or provides an old version, we recommend installing a recent ASDF so your implementation provides it, as explained below. If all fails, we recommend you load ASDF from source see Loading ASDF from source.
The ASDF source repository contains a script
bin/install-asdf-as-module that can help you upgrade your implementation’s ASDF.
It works on
Allegro CL, Clozure CL, CMU CL, ECL, GNU CLISP, LispWorks, MKCL, SBCL, SCL, XCL.
That’s all known implementations except ABCL, Corman CL, GCL, Genera, MCL, MOCL.
Happily, ABCL is usually pretty up to date and shouldn’t need that script.
GCL would be supported, except that so far is still lacking usable support for require
.
Corman CL, Genera, MCL are obsolete anyway.
MOCL is under development.
On an old version of an implementation that does not provide ASDF,
you may have to load ASDF 3 from source before you load that script.
The script relies on cl-launch
4 for command-line invocation,
which may depend on ASDF being checked out in ~/common-lisp/asdf/
(which we recommend anyway)
if your implementation doesn’t even have an ASDF 2.
If you don’t have cl-launch
,
you can instead (load "bin/install-asdf-as-module")
from your implementation’s REPL after loading ASDF from source.
Finally, if your implementation only provides ASDF 2, and you can’t or won’t upgrade it or override its ASDF module, you may simply configure ASDF to find a proper upgrade; however, to avoid issues with a self-upgrade in mid-build, you must make sure to upgrade ASDF immediately after requiring the builtin ASDF 2:
(require "asdf") ;; <--- insert programmatic configuration here if needed (asdf:load-system :asdf)
Next: Issues with upgrading ASDF, Previous: Upgrading ASDF, Up: Upgrading ASDF [Contents][Index]