Re: [quicklisp] Quicklisp error when building weblocks

61 views
Skip to first unread message

Zach Beane

unread,
Sep 10, 2012, 8:29:01 AM9/10/12
to quic...@googlegroups.com
Tiarnan O'Corrain <ocor...@gmail.com> writes:

> Hi--
>
> trying to build weblocks on SBCL 1.0.55 / Linux i686 I get the following error:
>
> ; Loading "weblocks"
> .....
> debugger invoked on a TYPE-ERROR in thread
> #<THREAD "main thread" RUNNING {AB4F959}>:
> The value #<HASH-TABLE :TEST EQUAL :COUNT 15 {B1E7151}> is not of type LIST.
>
> Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL.
>
> restarts (invokable by number or by possibly-abbreviated name):
> 0: [ABORT] Give up on "weblocks"
> 1: Exit debugger, returning to top level.
>
> (ASDF::SOURCE-REGISTRY)
> 0] b
> ((LABELS SB-IMPL::RESTART-LISP :IN SAVE-LISP-AND-DIE))
>
> This then messes up quicklisp, which returns this error when trying to build
> any system. As is obvious from the output, there's not much in the backtrace.
>
> A restart fixes that, but loading weblocks again will break quicklisp again.
>
> Any ideas of where to start? The error occurs with the current release of
> quicklisp, and with 2012-07-03.
>
> I tried swapping in a newer version of ASDF, but to no avail.
>
> Any ideas?

I don't think this is limited to weblocks. It looks like the ASDF
configuration is messed up in some way. I think you'd see a similar
problem when loading any system.

Are you using SBCL from sbcl.org, or is it from package manager?

Can you try loading nothing *but* quicklisp, e.g.

sbcl --no-userinit --no-sysinit --load ~/quicklisp/setup.lisp

And then tell me if you still get this failure?

Thanks,
Zach

Tiarnan O'Corrain

unread,
Sep 11, 2012, 6:13:34 AM9/11/12
to quic...@googlegroups.com, xa...@xach.com
Hi Zach--

yes, I'm afraid I do:

souk@cathycarman:~$ sbcl/bin/sbcl --no-userinit --no-sysinit --load ~/quicklisp/setup.lisp
This is SBCL 1.0.58, 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.
* (ql:quickload 'weblocks)
To load "weblocks":
  Load 1 ASDF system:
    weblocks
; Loading "weblocks"
....
debugger invoked on a TYPE-ERROR in thread
#<THREAD "main thread" RUNNING {AB4FA69}>:
  The value #<HASH-TABLE :TEST EQUAL :COUNT 15 {C5ED9E9}> is not of type LIST.

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

restarts (invokable by number or by possibly-abbreviated name):
  0: [ABORT] Give up on "weblocks"
  1:         Exit debugger, returning to top level.

(ASDF::SOURCE-REGISTRY)
0]

I'm using SBCL from sbcl.org, downloaded yesterday

$ sbcl/bin/sbcl --version
SBCL 1.0.58

regards

Tiarnan

Tiarnan O'Corrain

unread,
Sep 11, 2012, 7:14:22 AM9/11/12
to quic...@googlegroups.com, xa...@xach.com
Hi--

I did a bit more digging, and asdf::*asdf-version* was reporting 2.011.  Quicklisp provides ASDF 2.014.6.  

Moving $SBCL/lib/sbcl/asdf/asdf.fasl out of the way caused the newer version to be compiled and used.  Weblocks now installs properly.

Is this because I'm using a pre-compiled version of sbcl, or because there's no way of ensuring that quicklisp is running the version of ASDF it (sometimes) needs?

regards

Tiarnán

Zach Beane

unread,
Sep 11, 2012, 8:20:47 AM9/11/12
to Tiarnan O'Corrain, quic...@googlegroups.com
Tiarnan O'Corrain <ocor...@gmail.com> writes:

Something else seems screwy. SBCL 1.0.58 normally comes with ASDF 2.23,
not 2.011. And 2.011 should work fine, all other things being equal.

Is it possible you have a mixed-up installation with old fasls mixed in
with new ones, or something?

Zach
Reply all
Reply to author
Forward
0 new messages