hunchentoot doesn't start

18 views
Skip to first unread message

Exal de Jesus Garcia Carrillo

unread,
Nov 16, 2007, 3:51:07 AM11/16/07
to weblocks
Hey guys, I'm trying start working with weblocking but I have some
problems, so, when I try to start the weblocks I get the following:

CL-USER> (weblocks:start-weblocks)

debugger invoked on a SIMPLE-ERROR:
(A SIMPLE-ERROR was caught when trying to print *DEBUG-CONDITION* when
entering
the debugger. Printing was aborted and the SIMPLE-ERROR was stored in
SB-DEBUG::*NESTED-DEBUG-CONDITION*.)

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

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

((LAMBDA (HUNCHENTOOT::SOCKET &OPTIONAL "#<...>" . "#<...>"))
NIL
#<SIMPLE-ERROR {507FADA1}>)
0] 0



There is some additional configuration for hunchentoot for get it
work?, I have tried also as root, stop apache, and I get the same
error, any clues?

P.S. I'm using SBCL 1.0 on GNU/Linux PPC



regards, Exal.

Slobodan Blazeski

unread,
Nov 16, 2007, 5:00:19 AM11/16/07
to weblocks


On Nov 16, 9:51 am, Exal de Jesus Garcia Carrillo
There shouldn't be any additional configuration just asdf install all
the needed libraries and manually install newest version of weblocks.
With Ubuntu 7.10 and sbcl 1.0.11 everything works as a charm for me.
Try starting weblocks with (weblocks:start-weblocks :debug t) if it
doesn't start try first hunchentoot demo:
(asdf:oos 'asdf:load-op :hunchentoot-test)
(hunchentoot:start-server :port 4242)
Than go to http://localhost:4242/hunchentoot/test to check is
demo working

Slobodan

Exal de Jesus Garcia Carrillo

unread,
Nov 16, 2007, 11:00:21 AM11/16/07
to weblocks
On Nov 16, 4:00 am, Slobodan Blazeski <slobodan.blaze...@gmail.com>
wrote:
> Than go to 71http://localhost:4242/hunchentoot/test to check is
> demo working


Definitively there is a problem with the hunchentoot, when I do the
``(hunchentoot:start-server :port 4242)'' I dont get any response and
also never get the top level prompt again :-(

Exal de Jesus Garcia Carrillo

unread,
Nov 16, 2007, 11:17:22 AM11/16/07
to weblocks
On Nov 16, 4:00 am, Slobodan Blazeski <slobodan.blaze...@gmail.com>
wrote:

> Than go to 71http://localhost:4242/hunchentoot/test to check is
> demo working

Exal de Jesus Garcia Carrillo

unread,
Nov 16, 2007, 11:23:50 AM11/16/07
to weblocks
On Nov 16, 4:00 am, Slobodan Blazeski <slobodan.blaze...@gmail.com>
wrote:

> There shouldn't be any additional configuration just asdf install all
> the needed libraries and manually install newest version of weblocks.
> With Ubuntu 7.10 and sbcl 1.0.11 everything works as a charm for me.
> Try starting weblocks with (weblocks:start-weblocks :debug t) if it
> doesn't start try first hunchentoot demo:
> (asdf:oos 'asdf:load-op :hunchentoot-test)
> (hunchentoot:start-server :port 4242)
> Than go to 71http://localhost:4242/hunchentoot/test to check is
> demo working


I have fixed the problem with hunchentoot, but I still get the same
error, look:
indeed, the error is wen I load weblock


* (asdf:operate 'asdf:load-op 'weblocks)

[ things loaded correctly, but after begin the errors]

debugger invoked on a SIMPLE-ERROR:
(A SIMPLE-ERROR was caught when trying to print SB-DEBUG:*DEBUG-
CONDITION* when
entering the debugger. Printing was aborted and the SIMPLE-ERROR was
stored in
SB-DEBUG::*NESTED-DEBUG-CONDITION*.)

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 #<LOAD-OP NIL {509F63D9}> on
#<ASDF:CL-SOURCE-FILE "keyword" {50A5F7C9}>.
1: [ACCEPT] Continue, treating #<LOAD-OP NIL {509F63D9}> on
#<ASDF:CL-SOURCE-FILE "keyword" {50A5F7C9}> as having
been
successful.
2: [ABORT ] Exit debugger, returning to top level.

(SB-PCL::ACCESSOR-MISS #<error printing object>)
0] 1
STYLE-WARNING: implicitly creating new generic function WIDGET-
CONTINUATION
STYLE-WARNING:
implicitly creating new generic function (SETF WIDGET-CONTINUATION)

debugger invoked on a SIMPLE-ERROR:
(A SIMPLE-ERROR was caught when trying to print SB-DEBUG:*DEBUG-
CONDITION* when
entering the debugger. Printing was aborted and the SIMPLE-ERROR was
stored in
SB-DEBUG::*NESTED-DEBUG-CONDITION*.)

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 #<LOAD-OP NIL {509F63D9}> on
#<ASDF:CL-SOURCE-FILE "call-answer" {50A5F7E9}>.
1: [ACCEPT] Continue, treating #<LOAD-OP NIL {509F63D9}> on
#<ASDF:CL-SOURCE-FILE "call-answer" {50A5F7E9}> as
having been
successful.
2: [ABORT ] Exit debugger, returning to top level.

(SB-PCL::ACCESSOR-MISS #<error printing object>)
0] 1

debugger invoked on a SIMPLE-ERROR:
(A SIMPLE-ERROR was caught when trying to print SB-DEBUG:*DEBUG-
CONDITION* when
entering the debugger. Printing was aborted and the SIMPLE-ERROR was
stored in
SB-DEBUG::*NESTED-DEBUG-CONDITION*.)

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 #<LOAD-OP NIL {509F63D9}> on
#<ASDF:CL-SOURCE-FILE "default-application" {509FC919}>.
1: [ACCEPT] Continue, treating #<LOAD-OP NIL {509F63D9}> on
#<ASDF:CL-SOURCE-FILE "default-application" {509FC919}>
as having
been successful.
2: [ABORT ] Exit debugger, returning to top level.

(SB-PCL::ACCESSOR-MISS #<error printing object>)
0] 1
NIL
* (weblocks:start-weblocks :debug t)

debugger invoked on a SIMPLE-ERROR:
(A SIMPLE-ERROR was caught when trying to print *DEBUG-CONDITION* when
entering
the debugger. Printing was aborted and the SIMPLE-ERROR was stored in
SB-DEBUG::*NESTED-DEBUG-CONDITION*.)

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

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

((LAMBDA (HUNCHENTOOT::SOCKET &OPTIONAL "#<...>" . "#<...>"))
NIL
#<SIMPLE-ERROR {508EE8C9}>)
0]

Exal de Jesus Garcia Carrillo

unread,
Nov 16, 2007, 11:25:43 AM11/16/07
to weblocks
On Nov 16, 4:00 am, Slobodan Blazeski <slobodan.blaze...@gmail.com>
wrote:

> There shouldn't be any additional configuration just asdf install all
> the needed libraries and manually install newest version of weblocks.
> With Ubuntu 7.10 and sbcl 1.0.11 everything works as a charm for me.
> Try starting weblocks with (weblocks:start-weblocks :debug t) if it
> doesn't start try first hunchentoot demo:
> (asdf:oos 'asdf:load-op :hunchentoot-test)
> (hunchentoot:start-server :port 4242)
> Than go to 71http://localhost:4242/hunchentoot/test to check is
> demo working


I have fixed the problem with hunchentoot, but I still get the same
error, look:
indeed, the error is wen I load weblock


* (asdf:operate 'asdf:load-op 'weblocks)

[ things loaded correctly, but after begin the errors]

debugger invoked on a SIMPLE-ERROR:
(A SIMPLE-ERROR was caught when trying to print SB-DEBUG:*DEBUG-
CONDITION* when
entering the debugger. Printing was aborted and the SIMPLE-ERROR was
stored in
SB-DEBUG::*NESTED-DEBUG-CONDITION*.)

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 #<LOAD-OP NIL {509F63D9}> on
#<ASDF:CL-SOURCE-FILE "keyword" {50A5F7C9}>.
1: [ACCEPT] Continue, treating #<LOAD-OP NIL {509F63D9}> on
#<ASDF:CL-SOURCE-FILE "keyword" {50A5F7C9}> as having
been
successful.
2: [ABORT ] Exit debugger, returning to top level.

(SB-PCL::ACCESSOR-MISS #<error printing object>)
0] 1
STYLE-WARNING: implicitly creating new generic function WIDGET-
CONTINUATION
STYLE-WARNING:
implicitly creating new generic function (SETF WIDGET-CONTINUATION)

debugger invoked on a SIMPLE-ERROR:
(A SIMPLE-ERROR was caught when trying to print SB-DEBUG:*DEBUG-
CONDITION* when
entering the debugger. Printing was aborted and the SIMPLE-ERROR was
stored in
SB-DEBUG::*NESTED-DEBUG-CONDITION*.)

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 #<LOAD-OP NIL {509F63D9}> on
#<ASDF:CL-SOURCE-FILE "call-answer" {50A5F7E9}>.
1: [ACCEPT] Continue, treating #<LOAD-OP NIL {509F63D9}> on
#<ASDF:CL-SOURCE-FILE "call-answer" {50A5F7E9}> as
having been
successful.
2: [ABORT ] Exit debugger, returning to top level.

(SB-PCL::ACCESSOR-MISS #<error printing object>)
0] 1

debugger invoked on a SIMPLE-ERROR:
(A SIMPLE-ERROR was caught when trying to print SB-DEBUG:*DEBUG-
CONDITION* when
entering the debugger. Printing was aborted and the SIMPLE-ERROR was
stored in
SB-DEBUG::*NESTED-DEBUG-CONDITION*.)

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 #<LOAD-OP NIL {509F63D9}> on
#<ASDF:CL-SOURCE-FILE "default-application" {509FC919}>.
1: [ACCEPT] Continue, treating #<LOAD-OP NIL {509F63D9}> on
#<ASDF:CL-SOURCE-FILE "default-application" {509FC919}>
as having
been successful.
2: [ABORT ] Exit debugger, returning to top level.

(SB-PCL::ACCESSOR-MISS #<error printing object>)
0] 1
NIL
* (weblocks:start-weblocks :debug t)

debugger invoked on a SIMPLE-ERROR:
(A SIMPLE-ERROR was caught when trying to print *DEBUG-CONDITION* when
entering
the debugger. Printing was aborted and the SIMPLE-ERROR was stored in
SB-DEBUG::*NESTED-DEBUG-CONDITION*.)

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

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

((LAMBDA (HUNCHENTOOT::SOCKET &OPTIONAL "#<...>" . "#<...>"))
NIL
#<SIMPLE-ERROR {508EE8C9}>)
0]

Exal de Jesus Garcia Carrillo

unread,
Nov 16, 2007, 11:43:15 AM11/16/07
to weblocks
On Nov 16, 4:00 am, Slobodan Blazeski <slobodan.blaze...@gmail.com>
wrote:

> There shouldn't be any additional configuration just asdf install all
> the needed libraries and manually install newest version of weblocks.
> With Ubuntu 7.10 and sbcl 1.0.11 everything works as a charm for me.
> Try starting weblocks with (weblocks:start-weblocks :debug t) if it
> doesn't start try first hunchentoot demo:
> (asdf:oos 'asdf:load-op :hunchentoot-test)
> (hunchentoot:start-server :port 4242)
> Than go to 71http://localhost:4242/hunchentoot/test to check is
> demo working


I have fixed the problem with hunchentoot, but I still get the same
error, look:
indeed, the error is wen I load weblock


* (asdf:operate 'asdf:load-op 'weblocks)

[ things loaded correctly, but after begin the errors]

debugger invoked on a SIMPLE-ERROR:
(A SIMPLE-ERROR was caught when trying to print SB-DEBUG:*DEBUG-
CONDITION* when
entering the debugger. Printing was aborted and the SIMPLE-ERROR was
stored in
SB-DEBUG::*NESTED-DEBUG-CONDITION*.)

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 #<LOAD-OP NIL {509F63D9}> on
#<ASDF:CL-SOURCE-FILE "keyword" {50A5F7C9}>.
1: [ACCEPT] Continue, treating #<LOAD-OP NIL {509F63D9}> on
#<ASDF:CL-SOURCE-FILE "keyword" {50A5F7C9}> as having
been
successful.
2: [ABORT ] Exit debugger, returning to top level.

(SB-PCL::ACCESSOR-MISS #<error printing object>)
0] 1
STYLE-WARNING: implicitly creating new generic function WIDGET-
CONTINUATION
STYLE-WARNING:
implicitly creating new generic function (SETF WIDGET-CONTINUATION)

debugger invoked on a SIMPLE-ERROR:
(A SIMPLE-ERROR was caught when trying to print SB-DEBUG:*DEBUG-
CONDITION* when
entering the debugger. Printing was aborted and the SIMPLE-ERROR was
stored in
SB-DEBUG::*NESTED-DEBUG-CONDITION*.)

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 #<LOAD-OP NIL {509F63D9}> on
#<ASDF:CL-SOURCE-FILE "call-answer" {50A5F7E9}>.
1: [ACCEPT] Continue, treating #<LOAD-OP NIL {509F63D9}> on
#<ASDF:CL-SOURCE-FILE "call-answer" {50A5F7E9}> as
having been
successful.
2: [ABORT ] Exit debugger, returning to top level.

(SB-PCL::ACCESSOR-MISS #<error printing object>)
0] 1

debugger invoked on a SIMPLE-ERROR:
(A SIMPLE-ERROR was caught when trying to print SB-DEBUG:*DEBUG-
CONDITION* when
entering the debugger. Printing was aborted and the SIMPLE-ERROR was
stored in
SB-DEBUG::*NESTED-DEBUG-CONDITION*.)

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 #<LOAD-OP NIL {509F63D9}> on
#<ASDF:CL-SOURCE-FILE "default-application" {509FC919}>.
1: [ACCEPT] Continue, treating #<LOAD-OP NIL {509F63D9}> on
#<ASDF:CL-SOURCE-FILE "default-application" {509FC919}>
as having
been successful.
2: [ABORT ] Exit debugger, returning to top level.

(SB-PCL::ACCESSOR-MISS #<error printing object>)
0] 1
NIL
* (weblocks:start-weblocks :debug t)

debugger invoked on a SIMPLE-ERROR:
(A SIMPLE-ERROR was caught when trying to print *DEBUG-CONDITION* when
entering
the debugger. Printing was aborted and the SIMPLE-ERROR was stored in
SB-DEBUG::*NESTED-DEBUG-CONDITION*.)

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

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

((LAMBDA (HUNCHENTOOT::SOCKET &OPTIONAL "#<...>" . "#<...>"))
NIL
#<SIMPLE-ERROR {508EE8C9}>)
0]

Exal de Jesus Garcia Carrillo

unread,
Nov 16, 2007, 11:52:18 AM11/16/07
to weblocks
On Nov 16, 4:00 am, Slobodan Blazeski <slobodan.blaze...@gmail.com>
wrote:

> There shouldn't be any additional configuration just asdf install all
> the needed libraries and manually install newest version of weblocks.
> With Ubuntu 7.10 and sbcl 1.0.11 everything works as a charm for me.
> Try starting weblocks with (weblocks:start-weblocks :debug t) if it
> doesn't start try first hunchentoot demo:
> (asdf:oos 'asdf:load-op :hunchentoot-test)
> (hunchentoot:start-server :port 4242)
> Than go to 71http://localhost:4242/hunchentoot/test to check is
> demo working


I have fixed the problem with hunchentoot, but I still get the same
error, look:
indeed, the error is wen I load weblock


* (asdf:operate 'asdf:load-op 'weblocks)

[ things loaded correctly, but after begin the errors]

debugger invoked on a SIMPLE-ERROR:
(A SIMPLE-ERROR was caught when trying to print SB-DEBUG:*DEBUG-
CONDITION* when
entering the debugger. Printing was aborted and the SIMPLE-ERROR was
stored in
SB-DEBUG::*NESTED-DEBUG-CONDITION*.)

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 #<LOAD-OP NIL {509F63D9}> on
#<ASDF:CL-SOURCE-FILE "keyword" {50A5F7C9}>.
1: [ACCEPT] Continue, treating #<LOAD-OP NIL {509F63D9}> on
#<ASDF:CL-SOURCE-FILE "keyword" {50A5F7C9}> as having
been
successful.
2: [ABORT ] Exit debugger, returning to top level.

(SB-PCL::ACCESSOR-MISS #<error printing object>)
0] 1
STYLE-WARNING: implicitly creating new generic function WIDGET-
CONTINUATION
STYLE-WARNING:
implicitly creating new generic function (SETF WIDGET-CONTINUATION)

debugger invoked on a SIMPLE-ERROR:
(A SIMPLE-ERROR was caught when trying to print SB-DEBUG:*DEBUG-
CONDITION* when
entering the debugger. Printing was aborted and the SIMPLE-ERROR was
stored in
SB-DEBUG::*NESTED-DEBUG-CONDITION*.)

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 #<LOAD-OP NIL {509F63D9}> on
#<ASDF:CL-SOURCE-FILE "call-answer" {50A5F7E9}>.
1: [ACCEPT] Continue, treating #<LOAD-OP NIL {509F63D9}> on
#<ASDF:CL-SOURCE-FILE "call-answer" {50A5F7E9}> as
having been
successful.
2: [ABORT ] Exit debugger, returning to top level.

(SB-PCL::ACCESSOR-MISS #<error printing object>)
0] 1

debugger invoked on a SIMPLE-ERROR:
(A SIMPLE-ERROR was caught when trying to print SB-DEBUG:*DEBUG-
CONDITION* when
entering the debugger. Printing was aborted and the SIMPLE-ERROR was
stored in
SB-DEBUG::*NESTED-DEBUG-CONDITION*.)

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 #<LOAD-OP NIL {509F63D9}> on
#<ASDF:CL-SOURCE-FILE "default-application" {509FC919}>.
1: [ACCEPT] Continue, treating #<LOAD-OP NIL {509F63D9}> on
#<ASDF:CL-SOURCE-FILE "default-application" {509FC919}>
as having
been successful.
2: [ABORT ] Exit debugger, returning to top level.

(SB-PCL::ACCESSOR-MISS #<error printing object>)
0] 1
NIL
* (weblocks:start-weblocks :debug t)

debugger invoked on a SIMPLE-ERROR:
(A SIMPLE-ERROR was caught when trying to print *DEBUG-CONDITION* when
entering
the debugger. Printing was aborted and the SIMPLE-ERROR was stored in
SB-DEBUG::*NESTED-DEBUG-CONDITION*.)

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

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

((LAMBDA (HUNCHENTOOT::SOCKET &OPTIONAL "#<...>" . "#<...>"))
NIL
#<SIMPLE-ERROR {508EE8C9}>)
0]

Exal de Jesus Garcia Carrillo

unread,
Nov 16, 2007, 11:57:25 AM11/16/07
to weblocks
On Nov 16, 4:00 am, Slobodan Blazeski <slobodan.blaze...@gmail.com>
wrote:

> There shouldn't be any additional configuration just asdf install all
> the needed libraries and manually install newest version of weblocks.
> With Ubuntu 7.10 and sbcl 1.0.11 everything works as a charm for me.
> Try starting weblocks with (weblocks:start-weblocks :debug t) if it
> doesn't start try first hunchentoot demo:
> (asdf:oos 'asdf:load-op :hunchentoot-test)
> (hunchentoot:start-server :port 4242)
> Than go to 71http://localhost:4242/hunchentoot/test to check is
> demo working


I have fixed the problem with hunchentoot, but I still get the same
error, look:
indeed, the error is wen I load weblock


* (asdf:operate 'asdf:load-op 'weblocks)

[ things loaded correctly, but after begin the errors]

debugger invoked on a SIMPLE-ERROR:
(A SIMPLE-ERROR was caught when trying to print SB-DEBUG:*DEBUG-
CONDITION* when
entering the debugger. Printing was aborted and the SIMPLE-ERROR was
stored in
SB-DEBUG::*NESTED-DEBUG-CONDITION*.)

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 #<LOAD-OP NIL {509F63D9}> on
#<ASDF:CL-SOURCE-FILE "keyword" {50A5F7C9}>.
1: [ACCEPT] Continue, treating #<LOAD-OP NIL {509F63D9}> on
#<ASDF:CL-SOURCE-FILE "keyword" {50A5F7C9}> as having
been
successful.
2: [ABORT ] Exit debugger, returning to top level.

(SB-PCL::ACCESSOR-MISS #<error printing object>)
0] 1
STYLE-WARNING: implicitly creating new generic function WIDGET-
CONTINUATION
STYLE-WARNING:
implicitly creating new generic function (SETF WIDGET-CONTINUATION)

debugger invoked on a SIMPLE-ERROR:
(A SIMPLE-ERROR was caught when trying to print SB-DEBUG:*DEBUG-
CONDITION* when
entering the debugger. Printing was aborted and the SIMPLE-ERROR was
stored in
SB-DEBUG::*NESTED-DEBUG-CONDITION*.)

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 #<LOAD-OP NIL {509F63D9}> on
#<ASDF:CL-SOURCE-FILE "call-answer" {50A5F7E9}>.
1: [ACCEPT] Continue, treating #<LOAD-OP NIL {509F63D9}> on
#<ASDF:CL-SOURCE-FILE "call-answer" {50A5F7E9}> as
having been
successful.
2: [ABORT ] Exit debugger, returning to top level.

(SB-PCL::ACCESSOR-MISS #<error printing object>)
0] 1

debugger invoked on a SIMPLE-ERROR:
(A SIMPLE-ERROR was caught when trying to print SB-DEBUG:*DEBUG-
CONDITION* when
entering the debugger. Printing was aborted and the SIMPLE-ERROR was
stored in
SB-DEBUG::*NESTED-DEBUG-CONDITION*.)

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 #<LOAD-OP NIL {509F63D9}> on
#<ASDF:CL-SOURCE-FILE "default-application" {509FC919}>.
1: [ACCEPT] Continue, treating #<LOAD-OP NIL {509F63D9}> on
#<ASDF:CL-SOURCE-FILE "default-application" {509FC919}>
as having
been successful.
2: [ABORT ] Exit debugger, returning to top level.

(SB-PCL::ACCESSOR-MISS #<error printing object>)
0] 1
NIL
* (weblocks:start-weblocks :debug t)

debugger invoked on a SIMPLE-ERROR:
(A SIMPLE-ERROR was caught when trying to print *DEBUG-CONDITION* when
entering
the debugger. Printing was aborted and the SIMPLE-ERROR was stored in
SB-DEBUG::*NESTED-DEBUG-CONDITION*.)

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

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

((LAMBDA (HUNCHENTOOT::SOCKET &OPTIONAL "#<...>" . "#<...>"))
NIL
#<SIMPLE-ERROR {508EE8C9}>)
0]

Slobodan Blazeski

unread,
Nov 16, 2007, 12:12:45 PM11/16/07
to weblocks
If you are using latest sbcl 1.0.11, asdf-installed the latest
version of needed libraries, pulled newest repos of weblocks from
darcs, and the hunchentoot-test demo is working flawless. Than I
could only advice to rebuild all and try one more time. If it doesn't
help you'll have to wait for Slava.
If weblocks load but fails afterwards, try running the tests.

Slobodan

P.S.
And please stop triple posting

On Nov 16, 8:43 am, Exal de Jesus Garcia Carrillo

Exal de Jesus Garcia Carrillo

unread,
Nov 16, 2007, 1:17:04 PM11/16/07
to weblocks
On 16 nov, 11:12, Slobodan Blazeski <slobodan.blaze...@gmail.com>
wrote:

> If you are using latest sbcl 1.0.11, asdf-installed the latest
> version of needed libraries,

I have the latest version of SBCL (1.0) for my kind of processor
(Power PC).

>pulled newest repos of weblocks from
> darcs, and the hunchentoot-test demo is working flawless. Than I
> could only advice to rebuild all and try one more time.

I have fixed the hunchentoot problem, this works now.

> If it doesn't
> help you'll have to wait for Slava.

What/who is Slava?

> If weblocks load but fails afterwards, try running the tests.

Indeed weblocks doesn't load properly (AFAIK)

> P.S.
> And please stop triple posting

Sorry, was an accident.

Thanks, Exal.

Vyacheslav Akhmechet

unread,
Nov 16, 2007, 1:37:48 PM11/16/07
to webl...@googlegroups.com
Exal,

I don't think SBCL supports threads on PPC architectures. Weblocks can
only run on configurations that allow multithreading. Not being able
to get back to the prompt is probably a function of this.

I'm not sure why Weblocks doesn't load for you, but before you can get
that working try to find a hardware/software configuration that
supports threads.

Regards,
Slava Akhmechet

Exal de Jesus Garcia Carrillo

unread,
Nov 16, 2007, 1:49:20 PM11/16/07
to weblocks
On 16 nov, 12:37, "Vyacheslav Akhmechet" <coffee...@gmail.com> wrote:

> Exal,
>
> I don't think SBCL supports threads on PPC architectures. Weblocks can
> only run on configurations that allow multithreading. Not being able
> to get back to the prompt is probably a function of this.

mmmhh, you are right, SBCL do not support threading on PPC.

> I'm not sure why Weblocks doesn't load for you, but before you can get
> that working try to find a hardware/software configuration that
> supports threads.

:-(


Regards, Exal.

Slobodan Blazeski

unread,
Nov 16, 2007, 2:46:32 PM11/16/07
to weblocks


On Nov 16, 10:17 am, Exal de Jesus Garcia Carrillo
<exal.gar...@gmail.com> wrote:
> On 16 nov, 11:12, Slobodan Blazeski <slobodan.blaze...@gmail.com>
> wrote:
>
> > If you are using latest sbcl 1.0.11, asdf-installed the latest
> > version of needed libraries,
>
> I have the latest version of SBCL (1.0) for my kind of processor
> (Power PC).
Check does OpenMCL supports threading on PPC?
>
> >pulled newest repos of weblocks from
> > darcs, and the hunchentoot-test demo is working flawless. Than I
> > could only advice to rebuild all and try one more time.
>
> I have fixed the hunchentoot problem, this works now.
I doubt hunchentoot would be of any use in a single threaded
implementation.
Unless you're planning a single user web app :)
>
> > If it doesn't
> > help you'll have to wait for Slava.
>
> What/who is Slava?
Author of weblocks http://www.defmacro.org

Vyacheslav Akhmechet

unread,
Nov 16, 2007, 5:18:07 PM11/16/07
to webl...@googlegroups.com
On 11/16/07, Slobodan Blazeski <slobodan...@gmail.com> wrote:
> Check does OpenMCL supports threading on PPC?
Normally it does, but Exal is running PPC on Linux. I'm not sure if
OpenMCL has threading on this configuration...

> I doubt hunchentoot would be of any use in a single threaded
> implementation.
> Unless you're planning a single user web app :)

Actually, you can get very far with this setup. If you offload serving
of static content to Apache and dynamic content is relatively quick to
generate (which it normally is for web pages) you can get very high
throughput. This setup for weblocks will remain on wishlist for a
while, though.

Reply all
Reply to author
Forward
0 new messages