From: Robin L. P. <rlp...@di...> - 2008-12-16 04:27:48
|
I grabbed and installed http://prdownloads.sourceforge.net/sbcl/sbcl-1.0.22-x86-64-linux-binary.tar.bz2 today. After (finally!) getting all of weblocks' requirements in place, I get: debugger invoked on a SIMPLE-ERROR: You're trying to start Weblocks on SBCL without threading support. Recompile your SBCL with threads enabled. Why is that? -Robin -- They say: "The first AIs will be built by the military as weapons." And I'm thinking: "Does it even occur to you to try for something other than the default outcome?" -- http://shorl.com/tydruhedufogre http://www.digitalkingdom.org/~rlpowell/ *** http://www.lojban.org/ |
From: Nikodemus S. <nik...@ra...> - 2008-12-16 10:23:44
|
On Tue, Dec 16, 2008 at 6:27 AM, Robin Lee Powell <rlp...@di...> wrote: > > I grabbed and installed > http://prdownloads.sourceforge.net/sbcl/sbcl-1.0.22-x86-64-linux-binary.tar.bz2 > today. After (finally!) getting all of weblocks' requirements in > place, I get: > > debugger invoked on a SIMPLE-ERROR: > You're trying to start Weblocks on SBCL without threading > support. Recompile your SBCL with threads enabled. Threads are not enabled by default. (Though arguably they should be on Linux.) To get a threaded SBCL grab the sourcecode, do echo "(lambda (f) (cons :sb-thread f))" > customize-target-features.lisp build SBCL sh make.sh &> log and install it: sudo sh install.sh Cheers, -- Nikodemus |
From: Juho S. <js...@ik...> - 2008-12-16 12:35:16
|
"Nikodemus Siivola" <nik...@ra...> writes: > On Tue, Dec 16, 2008 at 6:27 AM, Robin Lee Powell > <rlp...@di...> wrote: > > > > I grabbed and installed > > http://prdownloads.sourceforge.net/sbcl/sbcl-1.0.22-x86-64-linux-binary.tar.bz2 > > today. After (finally!) getting all of weblocks' requirements in > > place, I get: > > > > debugger invoked on a SIMPLE-ERROR: > > You're trying to start Weblocks on SBCL without threading > > support. Recompile your SBCL with threads enabled. > > Threads are not enabled by default. (Though arguably they should be on > Linux.) But they are afaik intended to be on in the linux x86 and x86-64 binaries. So probably just a matter of whoever built the binary forgetting to switch it on. -- Juho Snellman |