You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
But the solution was to git clone the newest cl-environments.
After that, however, a new problem occurred while loading:
(SB-INT:%FIND-PACKAGE-OR-LOSE "CLAYLIB/WRAP")
0] ##########################################################################
; Loading "trivial-extensible-sequences"
[package org.shirakumo.trivial-extensible-sequences]
To load "claylib":
Load 1 ASDF system:
claylib
; Loading "claylib"
[package babel-encodings].........................
[package babel]...................................
..................................................
[package cffi-sys]................................
[package cffi-features]...........................
[package cffi]....................................
.............................
debugger invoked on a PACKAGE-DOES-NOT-EXIST in thread
#<THREAD tid=259 "main thread" RUNNING {7005B305C3}>:
The name "CLAYLIB/WRAP" does not designate any package.
Type HELP for debugger help, or (SB-EXT:EXIT) to exit from SBCL.
restarts (invokable by number or by possibly-abbreviated name):
0: [CONTINUE ] Use the current package, COMMON-LISP-USER.
1: [RETRY ] Retry finding the package.
2: [USE-VALUE ] Specify a different package
3: [RETRY ] Retry
compiling #<CL-SOURCE-FILE "claylib/wrap" "claylib-wrap">.
4: [ACCEPT ] Continue, treating
compiling #<CL-SOURCE-FILE "claylib/wrap" "claylib-wrap">
as having been successful.
5: Retry ASDF operation.
6: [CLEAR-CONFIGURATION-AND-RETRY] Retry ASDF operation after resetting the
configuration.
7: [ABORT ] Give up on "claylib"
8: [REGISTER-LOCAL-PROJECTS ] Register local projects and try again.
9: Exit debugger, returning to top level.
(SB-INT:%FIND-PACKAGE-OR-LOSE "CLAYLIB/WRAP")
\
I am on SBCL 2.4.2 .
The text was updated successfully, but these errors were encountered:
The first Issue I had was with cl-environments
alex-gutev/cl-environments#15
But the solution was to git clone the newest cl-environments.
After that, however, a new problem occurred while loading:
I am on SBCL 2.4.2 .
The text was updated successfully, but these errors were encountered: