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

Package error in SBCL port of NV-LENGTH, SB-EXT::ONCE-ONLY package lock error #68

Closed
markhdavid opened this issue Dec 14, 2024 · 5 comments

Comments

@markhdavid
Copy link

markhdavid commented Dec 14, 2024

Compiling Code/port.lisp in SBCL 2.4.11, while compiling Code/port.lisp, you get an error like

; compiling file "path/to/Code/port.lisp" (written 13 DEC 2024 08:32:28 PM):
; 
; caught ERROR:
;   READ error during COMPILE-FILE: Lock on package SB-EXT violated when interning ONCE-ONLY while in package FSET.
;   See also:
;     The SBCL Manual, Node "Package Locks"(in form starting at line: 376, column: 0, position: 11710)

Evidently, no symbol named "ONCE-ONLY" can be found in the SB-EXT package. The error happens while evaluating the defmacro for NV-LENGTH for the #+sbcl case only.

@markhdavid
Copy link
Author

There is a symbol named "ONCE-ONLY" in the SB-INT package in SBCL 2.4.11.

@markhdavid
Copy link
Author

Note the version of fset: "1.3.2" (the version currently used by quicklisp)

@markhdavid
Copy link
Author

Just noticed this is a duplicate of issue "fix: proper external package for sb-int:once-only #46", which was fixed in the current version of fset: "1.4.0". (It would be nice for quicklisp to use this later version.) Closing as duplicate.

@slburson
Copy link
Owner

@markhdavid Quicklisp is already on 1.4.2, which includes this fix. I think you need to update your Quicklisp installation.

@markhdavid
Copy link
Author

@markhdavid Quicklisp is already on 1.4.2, which includes this fix. I think you need to update your Quicklisp installation.

Think you're right, I'm livin' in the past

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