Rebuild After Upgrade to pacman 4.2.0 Fails with SB-KERNEL Error #83
Description
Hello,
I recently upgraded my computer with pak -Syu which included an update to pacman 4.2.0 libalpm version 9.0.0. Obviously, this bumped up the shared library needed from libalpm.so.8 to libalpm.so.9. Obviously pak was not aware of this, so when I tested it afterward, no biggy, I got the expected.
[me@laptop paktahn]$ pak -Syu
debugger invoked on a SIMPLE-ERROR in thread
#<THREAD "main thread" RUNNING {100479E6F3}>:
Error opening shared object "libalpm.so.8":
libalpm.so.8: cannot open shared object file: No such file or directory.
Type HELP for debugger help, or (SB-EXT:EXIT) to exit from SBCL.
restarts (invokable by number or by possibly-abbreviated name):
0: [CONTINUE ] Skip this shared object and continue.
1: [RETRY ] Retry loading this shared object.
2: [CHANGE-PATHNAME] Specify a different pathname to load the shared object from.
(SB-SYS:DLOPEN-OR-LOSE #S(SB-ALIEN::SHARED-OBJECT :PATHNAME #P"libalpm.so.8" :NAMESTRING "libalpm.so.8" :HANDLE NIL :DONT-SAVE NIL))
0]
No worries, I download the AUR tarball and download it to build the new version myself with makepkg like so.
[me@laptop paktahn]$ makepkg -s
==> Making package: paktahn 0.9.9.2-1 (Tue Dec 30 14:22:36 AST 2014)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Found paktahn-makedeps-0.9.3.tbz2
-> Found paktahn-0.9.9.2.tar.bz2
==> Validating source files with md5sums...
paktahn-makedeps-0.9.3.tbz2 ... Passed
paktahn-0.9.9.2.tar.bz2 ... Passed
==> Validating source files with sha1sums...
paktahn-makedeps-0.9.3.tbz2 ... Passed
paktahn-0.9.9.2.tar.bz2 ... Passed
==> Extracting sources...
-> Extracting paktahn-makedeps-0.9.3.tbz2 with bsdtar
-> Extracting paktahn-0.9.9.2.tar.bz2 with bsdtar
==> Removing existing $pkgdir/ directory...
==> Starting build()...
; compiling file "/home/me/Code/archlinux/builds/paktahn/src/clbuild.paktahn/source/cl-store/sbcl/custom.lisp" (written 12 AUG 2009 11:38:32 AM):
; compiling (IN-PACKAGE :CL-STORE)
; compiling (DEFUN CREATE-FLOAT-VALUES ...)
; compiling (DEFSTORE-CL-STORE (OBJ STRUCTURE-OBJECT ...) ...)
; compiling (DEFRESTORE-CL-STORE (STRUCTURE-OBJECT STREAM) ...)
; compiling (DEFUN GET-LAYOUT ...)
; compiling (DEFUN GET-INFO ...)
; compiling (DEFUN DD-NAME ...)
; compiling (DEFVAR *SBCL-STRUCT-INHERITS* ...)
; compiling (DEFSTRUCT (STRUCT-DEF #) ...)
; compiling (DEFUN INFO-OR-DIE ...)
; compiling (DEFUN SAVE-ABLE-SUPERS ...)
; compiling (DEFUN GET-SUPERS ...)
; compiling (DEFSTORE-CL-STORE (OBJ STRUCTURE-CLASS ...) ...)
; compiling (DEFSTORE-CL-STORE (OBJ STRUCT-DEF ...) ...);
; caught ERROR:
; READ error during COMPILE-FILE:
;
; Lock on package SB-KERNEL violated when interning CLASS-METHOD-DEFINITIONS
; while in package CL-STORE.
; See also:
; The SBCL Manual, Node "Package Locks"
;
; (in form starting at line: 76, column: 41, file-position: 2419)
; compilation aborted after 0:00:00.058
debugger invoked on a UIOP/LISP-BUILD:COMPILE-FILE-ERROR in thread
#<THREAD "main thread" RUNNING {1003017103}>:
COMPILE-FILE-ERROR while compiling #<NON-REQUIRED-FILE "cl-store" "custom">
Type HELP for debugger help, or (SB-EXT:EXIT) to exit from SBCL.
restarts (invokable by number or by possibly-abbreviated name):
0: [RETRY ] Retry
compiling #<NON-REQUIRED-FILE "cl-store" "custom">.
1: [ACCEPT ] Continue, treating
compiling #<NON-REQUIRED-FILE "cl-store" "custom">
as having been successful.
2: Retry ASDF operation.
3: [CLEAR-CONFIGURATION-AND-RETRY] Retry ASDF operation after resetting the
configuration.
4: [CONTINUE ] Ignore runtime option --eval "(asdf:oos 'asdf:load-op 'paktahn)".
5: [ABORT ] Skip rest of --eval and --load options.
6: Skip to toplevel READ/EVAL/PRINT loop.
7: [EXIT ] Exit SBCL (calling #'EXIT, killing the process).
(UIOP/LISP-BUILD:CHECK-LISP-COMPILE-RESULTS NIL T T "~/asdf-action::format-action/" ((#<ASDF/LISP-ACTION:COMPILE-OP > . #<CL-STORE.SYSTEM:NON-REQUIRED-FILE "cl-store" "custom">)))
0]
So is there something I am doing incorrectly? I tried in different clean directories, and BBS and an old Github commit indicate this should not be an issue for me. I am not sure what I am doing wrong. Thanks. I do have a quicklisp deploy turned on by default with SBCL, so I just want to throw that out there as it does mention this is part of the ASDF bootstrap process. I know it says kernel lock problem, so I may be way off base, but here is my ~/.sbclrc just in case.
;;; The following lines added by ql:add-to-init-file:
#-quicklisp
(let ((quicklisp-init (merge-pathnames ".ql/sbcl/setup.lisp"
(user-homedir-pathname))))
(when (probe-file quicklisp-init)
(load quicklisp-init)))