Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion Quicklisp error when building weblocks
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Zach Beane  
View profile  
 More options Sep 10 2012, 8:29 am
From: Zach Beane <x...@xach.com>
Date: Mon, 10 Sep 2012 08:29:01 -0400
Local: Mon, Sep 10 2012 8:29 am
Subject: Re: [quicklisp] Quicklisp error when building weblocks

Tiarnan O'Corrain <ocorr...@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


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.