loading :gtk fails

Bug #701079 reported by Boris Springborn
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
clg (Ubuntu)
New
Undecided
Unassigned

Bug Description

Trying to compile and load :gtk with sbcl using the command given in /usr/share/doc/cl-clg/README.gz leads to an error.
Expected: :gtk is compiled and loaded

$ lsb_release -rd
Description: Ubuntu 10.10
Release: 10.10

$ apt-cache policy cl-clg
cl-clg:
  Installed: 0.94~20090210-1
  Candidate: 0.94~20090210-1
  Version table:
 *** 0.94~20090210-1 0
        500 http://archive.ubuntu.com/ubuntu/ maverick/universe amd64 Packages
        100 /var/lib/dpkg/status

$ sbcl
This is SBCL 1.0.40.0.debian, an implementation of ANSI Common Lisp.
More information about SBCL is available at <http://www.sbcl.org/>.

SBCL is free software, provided as is, with absolutely no warranty.
It is mostly in the public domain; some portions are provided under
BSD-style licenses. See the CREDITS and COPYING files in the
distribution for more information.
* (asdf:oos 'asdf:load-op :gtk)

; loading system definition from /usr/share/common-lisp/systems/gtk.asd into
; #<PACKAGE "ASDF0">
; loading system definition from /usr/share/common-lisp/systems/clg-tools.asd
; into #<PACKAGE "ASDF1">
; registering #<SYSTEM CLG-TOOLS {1003617A61}> as CLG-TOOLS
; loading system definition from /usr/lib/sbcl/sb-posix/sb-posix.asd into
; #<PACKAGE "ASDF1">
; loading system definition from /usr/lib/sbcl/sb-grovel/sb-grovel.asd into
; #<PACKAGE "ASDF2">
; registering #<SYSTEM SB-GROVEL {1003142241}> as SB-GROVEL
; registering #<SYSTEM SB-POSIX {1002D09F11}> as SB-POSIX
; registering #<SYSTEM SB-POSIX-TESTS {100312BA71}> as SB-POSIX-TESTS
STYLE-WARNING: Couldn't grovel for SIGEMT (unknown to the C compiler).
STYLE-WARNING: Couldn't grovel for S_IFWHT (unknown to the C compiler).
STYLE-WARNING: Couldn't grovel for O_DIRECT (unknown to the C compiler).
; registering #<SYSTEM GTK {1002D11FC1}> as GTK
; loading system definition from /usr/share/common-lisp/systems/atk.asd into
; #<PACKAGE "ASDF0">
; registering #<SYSTEM ATK {1003595591}> as ATK
; loading system definition from /usr/share/common-lisp/systems/gdk.asd into
; #<PACKAGE "ASDF0">
; registering #<SYSTEM GDK {1003A7C681}> as GDK
; loading system definition from /usr/share/common-lisp/systems/cairo.asd into
; #<PACKAGE "ASDF0">
; registering #<SYSTEM CAIRO {10030BDEF1}> as CAIRO
; loading system definition from /usr/share/common-lisp/systems/glib.asd into
; #<PACKAGE "ASDF0">
; loading system definition from /usr/share/common-lisp/systems/gffi.asd into
; #<PACKAGE "ASDF1">
; registering #<SYSTEM GFFI {10035AFEB1}> as GFFI
; $ gcc -Wall -fPIC -O2 -o "/home/springb/.cache/common-lisp/sbcl-1.0.40.0.debian-linux-x86-64/usr/share/common-lisp/source/clg/gffi/alien/memory.o" -c "/usr/share/common-lisp/source/clg/gffi/alien/memory"
gcc: /usr/share/common-lisp/source/clg/gffi/alien/memory: No such file or directory
gcc: no input files

debugger invoked on a LOAD-SYSTEM-DEFINITION-ERROR in thread #<THREAD
                                                               "initial thread" RUNNING
                                                               {1002C99D91}>:
  Error while trying to load definition for system glib from pathname
  /usr/share/common-lisp/systems/glib.asd:
  erred while invoking #<COMPILE-OP NIL {10035E2891}> on
  #<C-SOURCE-FILE "memory" {10035CB321}>

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

restarts (invokable by number or by possibly-abbreviated name):
  0: [RETRY ] Retry performing #<COMPILE-OP NIL {10035E2891}> on
              #<C-SOURCE-FILE "memory" {10035CB321}>.
  1: [ACCEPT] Continue, treating #<COMPILE-OP NIL {10035E2891}> on
              #<C-SOURCE-FILE "memory" {10035CB321}> as having been successful.
  2: [ABORT ] Exit debugger, returning to top level.

((FLET #:LAMBDA1298) #<OPERATION-ERROR {10037DC301}>)
source:
; file: /usr/share/common-lisp/source/cl-asdf/asdf.lisp
(ERROR 'LOAD-SYSTEM-DEFINITION-ERROR :NAME NAME :PATHNAME ON-DISK :CONDITION
       CONDITION)
0]

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.