Bug 520337 - Load failure due to out-of-date SBCL internal command
Summary: Load failure due to out-of-date SBCL internal command
Keywords:
Status: CLOSED DUPLICATE of bug 499182
Alias: None
Product: Fedora
Classification: Fedora
Component: common-lisp-controller
Version: 11
Hardware: All
OS: Linux
low
high
Target Milestone: ---
Assignee: Anthony Green
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-08-30 21:02 UTC by Robert Andrew Uhl
Modified: 2010-02-18 18:17 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-02-18 18:17:24 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
Patch to use SB-IMPL::NATIVE-FILE-KIND (125 bytes, patch)
2009-09-21 18:59 UTC, Robert Andrew Uhl 		no flags Details | Diff
View All

Description Robert Andrew Uhl 2009-08-30 21:02:53 UTC 
Description of problem: common-lisp-controller no longer works due to sbcl update


Version-Release number of selected component (if applicable):


How reproducible: Every time


Steps to Reproduce:
1. start SBCL
2. (require :cl-ppcre) [or some other common-lisp-controller libary)
3. see failure
  
Actual results: SBCL errors


Expected results: loaded library


Additional info: This is due to SBCL renaming SB-UNIX:UNIX-FILE-KIND to SB-IMPL::NATIVE-FILE-KIND.

The easiest fix is to patch /usr/share/common-lisp/source/common-lisp-controller/post-sysdef-install.lisp to call SB-IMPL::NATIVE-FILE-KIND; without this fix CLC simply won't load.
Comment 1 Robert Andrew Uhl 2009-09-21 18:59:02 UTC 
Created attachment 361980 [details]
Patch to use SB-IMPL::NATIVE-FILE-KIND

This changes SB-UNIX:UNIX-FILE-KIND to SB-IMPL::NATIVE-FILE-KIND
Comment 2 Rex Dieter 2010-02-18 18:14:50 UTC 
Looks backwards to me?

--- file_not_specified_in_diff	
+++ file_not_specified_in_diff	
@@ -64,1 +64,1 @@ 
-	    (sb-impl::native-file-kind (namestring directory)))
+	    (sb-unix:unix-file-kind (namestring directory)))
Comment 3 Rex Dieter 2010-02-18 18:17:24 UTC 
ok, looks like the same stuff as bug #499182

*** This bug has been marked as a duplicate of bug 499182 ***
Note You need to log in before you can comment on or make changes to this bug.