... | ... | @@ -23,7 +23,7 @@ The following piece of code will also work on much older versions, though. |
|
|
|
|
|
### My favourite lisp implementation uses an old version of ASDF. What can I do?
|
|
|
|
|
|
If your current working directory is main directory of an ASDF clond, please first run
|
|
|
If your current working directory is main directory of an ASDF clone, please first run
|
|
|
```shell
|
|
|
git checkout release
|
|
|
make ext
|
... | ... | @@ -34,7 +34,7 @@ If you quickly mean to test if the old version of ASDF (and thus UIOP) your lisp |
|
|
```shell
|
|
|
make
|
|
|
```
|
|
|
to produce a build/asdf.lisp which you can then use in ways like this: `sbcl --load build/asdf.lisp --load ~/code-that-was-causing-errors.lisp
|
|
|
to produce a build/asdf.lisp which you can then use in ways like this: `sbcl --load build/asdf.lisp --load ~/code-that-was-causing-errors.lisp`
|
|
|
|
|
|
The proper solution for permanently upgrading the bundled ASDF version of your lisp implementation, however, would be, depending on which one you're on, something like
|
|
|
```shell
|
... | ... | @@ -43,7 +43,7 @@ ecl --load ./tools/asdf-tools -- install-asdf ecl # note the double-dash |
|
|
sbcl --load ./tools/asdf-tools install-asdf sbcl
|
|
|
```
|
|
|
|
|
|
The fact fact that your implementation occurs twice in each call is not by accident: The first is used to compile the lisp-code used to run install-asdf; the second is the target you're upgrading. They need not be identical; in particular, you could use sbcl to upgrade cmucl's asdf via
|
|
|
The fact that your implementation occurs twice in each call is not by accident: The first is used to compile the lisp-code that makes up install-asdf; the second is the target you're upgrading. They need not be identical; in particular, you could use sbcl to upgrade cmucl's asdf via
|
|
|
```shell
|
|
|
sbcl --load ./tools/asdf-tools install-asdf cmucl
|
|
|
```
|
... | ... | |