[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#492740: cl-f2cl: does not compile with sbcl

Package: cl-f2cl
Version: 20080222-1
Severity: important


I'm not sure if this is an sbcl problem or an f2cl problem.

(require 'f2cl) 

fails in sbcl- 

the last part of the output is

; compiling (DEFMACRO F2CL-SET-STRING ...)
; compiling (DEFUN F2CL-STRING ...)
; compiling (DEFUN D1MACH ...)
; compiling (DEFUN R1MACH ...)
; compiling (DEFUN I1MACH ...)
; compiling (DEFUN STOP ...)

; /var/cache/common-lisp-controller/1266/sbcl/cl-f2cl/macros.fasl written
; compilation finished in 0:00:00
   COMPILE-FILE warned while performing #<COMPILE-OP NIL {ABF30F1}> on
   #<CL-SOURCE-FILE "macros" {AC6E1D9}>.

debugger invoked on a ASDF:COMPILE-FAILED in thread #<THREAD "initial thread" RUNNING {A8346D1}>:
  erred while invoking #<COMPILE-OP NIL {ABF30F1}> on
  #<CL-SOURCE-FILE "macros" {AC6E1D9}>

Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL.

restarts (invokable by number or by possibly-abbreviated name):
  0: [TRY-RECOMPILING] Try recompiling macros
  1: [RETRY          ] Retry performing #<ASDF:COMPILE-OP NIL {ABF30F1}> on
                       #<ASDF:CL-SOURCE-FILE "macros" {AC6E1D9}>.
  2: [ACCEPT         ] Continue, treating #<ASDF:COMPILE-OP NIL {ABF30F1}> on
                       #<ASDF:CL-SOURCE-FILE "macros" {AC6E1D9}> as having been
  3: [ABORT          ] Exit debugger, returning to top level.

 #<unavailable argument>
 #<unavailable argument>
 #<ASDF:CL-SOURCE-FILE "macros" {AC6E1D9}>)

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.25-2-686 (SMP w/2 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages cl-f2cl depends on:
ii  common-lisp-controller        6.16       Common Lisp source and compiler ma

cl-f2cl recommends no packages.

cl-f2cl suggests no packages.

-- no debconf information

Reply to: