You have another ASDF somewhere, like ~/common-lisp/asdf.
When you load some system it first checks for newer ASDF and loads it.
For some reason it fails with unbound slot STAMP in ACTION-STATUS object.
When trying to print that object stack blows up.
I have actually reproduced this. All works fin
ot;querent"
An:
Betreff: ASDF problem on second load of ECL
Datum: Do., Feb. 27, 2020 10:57
Hi there,
I am just trying to use ECL for a little project of mine, but I have a problem.
Immediately after installation, things seem to work fine. I can run things,
produce executables, etc
Aha!
A locate asdf.lisp tells me of an asdf.lisp in ~/.local/share/ which according
to the comment is version 2.26, which having read the documentation I
understand to be quite old!
I also removed the cl-asdf Ubuntu package. One of them was the culprit.
OK, now to figure out how to use asdf
Hey querent,
could it be, that you have two ASDF versions loaded on top of each
other? i.e asdf.lisp in your ~/common-lisp/ directory or something in
this spirit.
Best regards,
Daniel
--
Daniel Kochmański ;; aka jackdaniel | Przemyśl, Poland
TurtleWare - Daniel Kochmański | www.turtleware.
Hi there,
I am just trying to use ECL for a little project of mine, but I have a problem.
Immediately after installation, things seem to work fine. I can run things,
produce executables, etc.
However, the second time I load ECL I get the error listed below.
Deleting .cache/common-lisp/ecl-16.
