Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When running ros install arrival , I get an error related to log4cl #41

Open
aymeric75 opened this issue Apr 1, 2023 · 1 comment
Open

Comments

@aymeric75
Copy link

Hello,

When running ros install arrival , I get an error related to log4cl


To load "arrival":
  Load 1 ASDF system:
    arrival
; Loading "arrival"
..[1/3] System 'arrival' found. Loading the system..
; 
; caught ERROR:
;   READ error during COMPILE-FILE:
;   
;     Lock on package SB-C violated when interning LAMBDA-PARENT while in package
;     LOG4CL-IMPL.
;   See also:
;     The SBCL Manual, Node "Package Locks"
;   
;     (in form starting at line: 99, column: 0, position: 3779)
Aborted during step [1/3].
Unhandled UIOP/LISP-BUILD:COMPILE-FILE-ERROR in thread #<SB-THREAD:THREAD tid=80526 "main thread" RUNNING
                                                          {10044A0113}>:
  COMPILE-FILE-ERROR while
  compiling #<CL-SOURCE-FILE "log4cl" "src" "naming-sbcl">

Any idea where this comes from ?

Thanks

@scymtym
Copy link
Contributor

scymtym commented Apr 2, 2023

Please note that this repository is not maintained anymore. Maintenance of this library is performed in the https://github.com/sharplispers/log4cl fork.

I don't know what arrival is or how ros loads it but I suspect that the problem stems from the fact that log4cl uses internal interfaces of SBCL which changed in recent SBCL versions. The two solutions I can think of are

  1. Use an older SBCL version
  2. Use the master version of log4cl (from the https://github.com/sharplispers/log4cl fork)

Hope this helps.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants