Sounds like you've got a version of weblocks that depends on  
hunchentoot 0.15.x but have 1.0 installed.

Ian

On Feb 24, 2009, at 2:23 PM, Saikat Chakrabarti wrote:

>
> you tried installing weblocks on ubuntu?? where?
>
> On Tue, Feb 24, 2009 at 6:11 AM, Divia <[email protected]> wrote:
>>
>> So far, I've been doing my Weblocks development on OS X, and my setup
>> has been working great.  However, today I tried to install Weblocks  
>> on
>> Ubuntu, and I'm running into some problems.  First, I installed
>> weblocks and prevalence, updated clsql for clsql-fluid, and installed
>> bordeaux threads, just as I had done on my Mac.  Then I got the error
>> component :USOCKET not found, and installed usocket too.  After  
>> having
>> done that, a lot more packages compiled successfully, but I still got
>> this error:
>>
>> ;     SB-INT:SIMPLE-READER-PACKAGE-ERROR at 437 (line 14, column 28)
>> on #<SB-SYS:FD-STREAM for "file /home/smee/clbuild/source/weblocks/ 
>> src/
>> debug-mode.lisp" {100437C231}>:
>> ;       package "HUNCHENTOOT-MP" not found
>> ; compilation aborted after 0:00:00
>>
>> WARNING:
>>   COMPILE-FILE warned while performing #<COMPILE-OP NIL {1002CF3021}>
>> on
>>   #<CL-SOURCE-FILE "debug-mode" {10029E26C1}>.
>>
>> debugger invoked on a ASDF:COMPILE-FAILED in thread #<THREAD "initial
>> thread" RUNNING {100266B2E1}>:
>>  erred while invoking #<COMPILE-OP NIL {1002CF3021}> on
>>  #<CL-SOURCE-FILE "debug-mode" {10029E26C1}>
>>
>> II'm pretty stuck trying to figure this out, so I'd be extremely
>> grateful for any insights anyone might have as to why this is
>> happening.  I've been searching for stuff about hunchentoot-mp, but I
>> haven't found anything that made sense to me yet, so I'm worried I'm
>> on the wrong track. Thanks very much,
>>
>> Divia
>>>
>>
>
> >


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"weblocks" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/weblocks?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to