Package: cl-clg
Version: 0.94~20090210-1
Followup-For: Bug #646638
The problem mentionned by the submitter can be easily fixed by adding the
relevant load/require lines at the top of hello-world.lisp.
For SBCL, one just needs to add:
(require :asdf)
(require :gtk)
However, with this fix, the GTK package is seen by the CL machine but fails to
compile:
; compiling file "/usr/share/common-lisp/source/clg/tools/asdf-extensions.lisp"
(written 16 MAY 2009 05:55:45 PM):
; compiling (IN-PACKAGE :ASDF)
; compiling (USE-PACKAGE :PKG-CONFIG)ASDF could not load gtk because
Error while trying to load definition for system gtk from pathname
/usr/share/common-lisp/source/clg/gtk/gtk.asd:
USE-PACKAGE #<PACKAGE "PKG-CONFIG"> causes name-conflicts in
#<PACKAGE "ASDF"> between the following symbols:
SB-INT:FEATUREP, ASDF::FEATUREP
See also:
The ANSI Standard, Section 11.1.1.2.5.
unhandled LOAD-SYSTEM-DEFINITION-ERROR in thread #<SB-THREAD:THREAD
"initial thread" RUNNING
{1002998F43}>:
Error while trying to load definition for system gtk from pathname
/usr/share/common-lisp/source/clg/gtk/gtk.asd:
USE-PACKAGE #<PACKAGE "PKG-CONFIG"> causes name-conflicts in
#<PACKAGE "ASDF"> between the following symbols:
SB-INT:FEATUREP, ASDF::FEATUREP
See also:
The ANSI Standard, Section 11.1.1.2.5
This problem is clearly of RC severity, since the package is unusable. I think
either the present bug should be closed and another RC bug be opened, or the
present bug should be retitled.
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (990, 'testing'), (600, 'unstable'), (550, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.1.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages cl-clg depends on:
ii common-lisp-controller 7.8
ii libgtk2.0-dev 2.24.8-2
cl-clg recommends no packages.
cl-clg suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
