Just to be more clear: quit everything before trying those steps. And a handy tip for the debugger is CTRL-D will get you out if pressed repeatedly (though you'll lose valuable info that might help you crack the problem, but which can be confusing to newbies (was to me!)).
It seems you are one step away from getting to the weblocks demo, that is, fixing the missing sb-posix library. Also, the result of *features* at the REPL should contain at least threads. Here is mine, you can see :SB-THREAD -- weblocks requires threads to perform, though it'll run (and carp) without threads. CL-USER(1): *features* (:SB-BSD-SOCKETS-ADDRINFO :ASDF :ANSI-CL :COMMON-LISP :SBCL :SB- DOC :SB-TEST :SB-LDB :SB-THREAD :SB-LUTEX :SB-PACKAGE-LOCKS :SB-UNICODE :SB-EVAL :SB-SOURCE-LOCATIONS :IEEE-FLOATING-POINT :DARWIN :X86 :UNIX :MACH- O :BSD :DARWIN :MACH-EXCEPTION-HANDLER :SB-LUTEX :RESTORE-FS-SEGMENT-REGISTER-FROM-TLS :GENCGC :STACK-GROWS-DOWNWARD- NOT-UPWARD :C-STACK-IS-CONTROL-STACK :COMPARE-AND-SWAP-VOPS :UNWIND-TO-FRAME-AND- CALL-VOP :RAW-INSTANCE-INIT-VOPS :STACK-ALLOCATABLE-CLOSURES :ALIEN-CALLBACKS :CYCLE-COUNTER :LINKAGE-TABLE :OS-PROVIDES-DLOPEN :OS-PROVIDES-DLADDR :OS-PROVIDES-PUTWC :OS-PROVIDES-BLKSIZE-T :OS-PROVIDES-SUSECONDS-T) CL-USER(2): --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
