Closed sabracrolleton closed 6 years ago
Problem is in string-case (which is pulled in by depending on serapeum) and latest version of sbcl. It has been flagged as an issue in that package. Not sure what users can do about it until string-case is fixed.
I'm pretty sure string-case is BSD, so if it doesn't get fixed in the nearish future I'll incorporate a fixed version into Serapeum.
On Thu, Jun 14, 2018 at 11:43 PM Sabra Crolleton notifications@github.com wrote:
Problem is in string-case (which is pulled in by depending on serapeum) and latest version of sbcl. It has been flagged as an issue in that package. Not sure what users can do about it until string-case is fixed.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/ruricolist/spinneret/issues/24#issuecomment-397511888, or mute the thread https://github.com/notifications/unsubscribe-auth/AAXwKCzB_f3sE4UEUP1eIATLy2MuWSPmks5t8ztkgaJpZM4Uo_e2 .
This has been fixed upstream, so I'm closing this issue.
sbcl version 1.4.8
To load "spinneret": Load 1 ASDF system: spinneret ; Loading "spinneret" .................................................. [package string-case]. ; ; caught ERROR: ; READ error during COMPILE-FILE: ;
; Lock on package SB-VM violated when interning XOR while in package ; STRING-CASE. ; See also: ; The SBCL Manual, Node "Package Locks" ;
; (in form starting at line: 246, column: 0, position: 10257)
Have not tried other versions of sbcl