sbcl 2.2.7 does not compile latest usocket-0.8.4 on Windows

Bug #1983355 reported by il71
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
SBCL
Invalid
Undecided
Unassigned

Bug Description

(ql:quickload :usocket)
To load "usocket":
  Load 1 ASDF system:
    usocket
; Loading "usocket"
[package split-sequence]..........................
[package usocket]........;
; caught ERROR:
; READ error during COMPILE-FILE:
;
; Lock on package SB-ALIEN violated when interning HINSTANCE while in package
; USOCKET.
; See also:
; The SBCL Manual, Node "Package Locks"
;
; (in form starting at line: 748, column: 0, position: 29389)

There is

(define-alien-type hinstance signed)

in sbcl's win32-foreign-load.lisp

The file is compiled during build, but there is no such symbol in SB-ALIEN:

(find-symbol "HINSTANCE" (find-package "SB-ALIEN"))
NIL
NIL

sbcl-2.2.6:
(find-symbol "HINSTANCE" (find-package "SB-ALIEN"))
SB-ALIEN::HINSTANCE
:INTERNAL

Revision history for this message
Stas Boukarev (stassats) wrote :

It's more of a usocket problem.

Changed in sbcl:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers