1

This compiles fine on ccl, but fails with a circular ref. error on SBCL:

kp.asd: (in-package :asdf) (defsystem kp :components ((:module "utils" :components ((:file "utils") )) )) (load-system :kp) ------------------------ utils.lisp: (defpackage :utils) (in-package :utils) (defvar *kp-version-utime* (get-universal-time)) ------------------------ Error reported by SBCL: debugger invoked on a LOAD-SYSTEM-DEFINITION-ERROR in thread #<THREAD "main thread" RUNNING {10005E85B3}>: Error while trying to load definition for \ system kp from pathname /var/www/ai/insights/kp.asd: Circular dependency: ((#<DEFINE-OP > . #<SYSTEM "kp">) (#<LOAD-OP > . #<SYSTEM "kp">) (#<LOAD-OP\ > . #<MODULE "kp" "utils">) (#<LOAD-OP > . #<CL-SOURCE-FILE "kp" "utils" "utils">) (#<PREPARE-OP > . #<CL-SOURCE-FILE "kp" "utils" "utils">) (#<PREP\ ARE-OP > . #<MODULE "kp" "utils">) (#<PREPARE-OP > . #<SYSTEM "kp">))

(It looks like your post is mostly code; please add some more details.)

Improve this question

2 Answers 2

Reset to default
2 
(load-system :kp)

You should not have this in an ASDF declaration. Better not consider a system definition as a Lisp program, only as a declarative way of stating your dependencies.

If, during the declaration of the system, you also need to load another system, then that system becomes a dependency. What happens most likely is that SBCL consider the file as a whole when evaluating it, and while loading kp, you ask it to load kp, which is indeed a circular dependency. Maybe CCL silently consider the file already loaded, I don't know.

If you remove it, entering (ql:quickload :kp) in the REPL works perfectly fine. Also, the (in-package :asdf) is useless (and if provided, it should be asdf-user)

Improve this answer
Sign up to request clarification or add additional context in comments.

4 Comments

Thanks, but now I get: ((LABELS QUICKLISP-CLIENT::RECURSE :IN QUICKLISP-CLIENT::COMPUTE-LOAD-STRATEGY) "kp") (same if I do it from the repl interactively). And (asdf:operate 'asdf:load-op :kp) gives: ((:METHOD ASDF/OPERATE:OPERATE (SYMBOL T)) ASDF/LISP-ACTION:LOAD-OP :KP) [fast-method] error finding frame source: Bogus form-number: the source file has probably changed too much to cope with.
If you start a second SBCL process and run the command, does it still happen? Or if you touch the .asd file to chang its timestamp and recompile? That a bit hard to debug without more information.
Got this to work, but DO need to include (in-package :asdf) AND load the .asd file explicitly. Thanks for your help.
If you load the file directly, then yes changing the package is necessary, but the intended usage is not to load asd files manually. If you can get it working that's fine but that may hide an unresolved problem. Good luck.
-1

Your .asd is invalid and deserves to lose.

Do you have an old CCL with ASDF 3.2 or earlier? Then it fails to detect the bug in your .asd. ASDF 3.3 correctly detects circular dependencies in the loading of .asd files.

Improve this answer

Comments

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.