Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 65872 - sbcl 0.8.13 and 0.8.14 can't install common-lisp-controller
Summary: sbcl 0.8.13 and 0.8.14 can't install common-lisp-controller
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Development (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Gentoo Lisp Project
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-09-29 20:32 UTC by Win Treese
Modified: 2004-11-15 20:01 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
Version information (aa,1.89 KB, text/plain)
2004-10-04 19:46 UTC, Win Treese
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Win Treese 2004-09-29 20:32:48 UTC
When sbcl tries to install common-lisp-controller, it fails when redefining
REQUIRE because sbcl 0.8.13 added the ability to lock packages against
modification. This is hard to see in the build because the error messages are
buried (and the installation code traps the error as well, with the details
not printed). The error that is printed is merely:

Error during init of common-lisp-controller
mv: cannot stat `sbcl-new.core': No such file or directory
FAILED
ebuild.sh: Compiler sbcl installed

Note also that the driver script doesn't catch the failure, so it later
looks like everything succeeded.

This problem can also manifest itself as a failure to load swank when
using SLIME. The underlying problem in that case is that swank isn't built
because the common-lisp-controller doesn't work, but again the driver scripts
don't notice the errors and everything looks OK from a quick glance.


Reproducible: Always
Steps to Reproduce:
1. emerge sbcl

Actual Results:  
sbcl appears to be installed, and it generally works correctly, but
the common-lisp-controller installation for sbcl is not built properly.
The errors described above show up in the log of the build if one looks
closely.


Expected Results:  
A simple fix is to unlock the COMMON-LISP package in common-lisp-controller.lisp:

--- common-lisp-controller.lisp~        2004-09-29 22:04:23.000000000 -0400
+++ common-lisp-controller.lisp 2004-09-29 22:42:21.000000000 -0400
@@ -121,6 +121,7 @@
 
 Returns nothing"
   ;; force both parameters to directories...
+  (sb-ext:unlock-package "COMMON-LISP")
   (let* ((fasl-root (pathname-dir-only fasl-root))
          (s-root (pathname-dir-only source-root))
          (source-root (make-pathname
Comment 1 Matthew Kennedy (RETIRED) gentoo-dev 2004-10-04 18:42:13 UTC
Win, what version of cl-asdf, cl-defsystem3 and common-lisp-controller are you using?  Please also attach the output of emerge --info 
Comment 2 Win Treese 2004-10-04 19:46:42 UTC
Created attachment 41117 [details]
Version  information

Version details (sorry, should have put these in to start with!)
Comment 3 Matthew Kennedy (RETIRED) gentoo-dev 2004-11-14 14:55:19 UTC
*common-lisp-controller-3.91 (01 Aug 2004)

  01 Aug 2004; <mkennedy@gentoo.org> +files/3.91/clc-send-command,
  +files/3.91/common-lisp-controller-gentoo.patch,
  +common-lisp-controller-3.91.ebuild:
  New upstream version; Required by SBCL w/ package locking

This version of the controller should resolve this problem.  Are you still encountering a problem?  I'll resolve this for now, feel free to reopen if necessary.
Comment 4 Win Treese 2004-11-15 20:01:01 UTC
The new version seems to work just fine. Thanks!