Hi there,
I installed sbcl on:
$ uname -r
2.4.31-grsec
and it complains:
$ sbcl
fatal error encountered in SBCL pid 7886(tid 16384):
This version of SBCL is compiled with threading support, but your kernel
is too old to support this.
Please use a more recent kernel or a version of SBCL without threading
support.
Now, does anybody know which version of sbcl should I use and where to
obtain it, since I'm not able to migrate to 2.6 kernel?
--
"Now the storm has passed over me
I'm left to drift on a dead calm sea
And watch her forever through the cracks in the beams
Nailed across the doorways of the bedrooms of my dreams"
Compiling SBCL from source is, in fact, very easy.
Just grab the source run and run a simple shell script.
Just make sure you disable the threading support.
But you need to have another Lisp in order to build SBCL, so may be
CLISP probably works for building SBCL.
<·········@net4u.hr> wrote:
> fatal error encountered in SBCL pid 7886(tid 16384):
> This version of SBCL is compiled with threading support, but your kernel
> is too old to support this.
> Please use a more recent kernel or a version of SBCL without threading
> support.
>
> Now, does anybody know which version of sbcl should I use and where to
> obtain it, since I'm not able to migrate to 2.6 kernel?
Binaries for old releases are available from the sourceforge download
page, <http://sourceforge.net/project/showfiles.php?group_id=1373>.
0.9.1 and earlier should probably work on your system. If you want to
use a newer version of SBCL (recommended), compiling from sources
without thread support is the way to go.
--
Juho Snellman
On 21 Nov 2005 14:00:23 GMT
Juho Snellman (······@iki.fi) said...
> <·········@net4u.hr> wrote:
> > fatal error encountered in SBCL pid 7886(tid 16384):
> > This version of SBCL is compiled with threading support, but your kernel
> > is too old to support this.
> > Please use a more recent kernel or a version of SBCL without threading
> > support.
> >
> > Now, does anybody know which version of sbcl should I use and where to
> > obtain it, since I'm not able to migrate to 2.6 kernel?
>
> Binaries for old releases are available from the sourceforge download
> page, <http://sourceforge.net/project/showfiles.php?group_id=1373>.
> 0.9.1 and earlier should probably work on your system. If you want to
> use a newer version of SBCL (recommended), compiling from sources
> without thread support is the way to go.
Can I use 0.9.1 to compile the most recent release?
--
"Now the storm has passed over me
I'm left to drift on a dead calm sea
And watch her forever through the cracks in the beams
Nailed across the doorways of the bedrooms of my dreams"
On Mon, 21 Nov 2005 22:07:45 +0100
Nikola Skoric (·········@net4u.hr) said...
> On 21 Nov 2005 14:00:23 GMT
> Juho Snellman (······@iki.fi) said...
> > <·········@net4u.hr> wrote:
> > > Now, does anybody know which version of sbcl should I use and where to
> > > obtain it, since I'm not able to migrate to 2.6 kernel?
> >
> > Binaries for old releases are available from the sourceforge download
> > page, <http://sourceforge.net/project/showfiles.php?group_id=1373>.
> > 0.9.1 and earlier should probably work on your system. If you want to
> > use a newer version of SBCL (recommended), compiling from sources
> > without thread support is the way to go.
>
> Can I use 0.9.1 to compile the most recent release?
It's realy lame to quote yourself, but I just forgot to ask: is there a
way to exclude some parts of SBCL when compiling? For instance, I don't
need CLOS right now, and every kB of disc space is of great importance
for me...
--
"Now the storm has passed over me
I'm left to drift on a dead calm sea
And watch her forever through the cracks in the beams
Nailed across the doorways of the bedrooms of my dreams"
In article <··························@news.htnet.hr>,
Nikola Skoric <·········@net4u.hr> wrote:
> It's realy lame to quote yourself, but I just forgot to ask: is there a
> way to exclude some parts of SBCL when compiling? For instance, I don't
> need CLOS right now, and every kB of disc space is of great importance
> for me...
For some things you can turn them off in your
customize-target-features.lisp file. See the INSTALL file, section 2.2,
"Customizing SBCL". For example, removing :sb-doc will remove all
docstrings, and adding :sb-fluid will remove most inline declarations
(probably making things completely glacial in the process). See
base-target-features.lisp-expr for a documented list.
However, I don't think there's an easy way to get rid of CLOS. You can
play around with src/cold/warm.lisp, as PCL is loaded from there in warm
init, but be warned that a CLOS-less SBCL will have a very sad user
experience (PRINT-OBJECT won't work, among other things - hope you like
looking at structure internals!), and will be completely unusable with
Slime and most other modern CL software.
You can experience some of this yourself by compiling sbcl and then
loading the cold core that's created by GENESIS (which is before PCL) by
running "./src/runtime/sbcl --core ./output/cold-sbcl.core".
Here's a preview: :-)
* (/ 2 0)
[...]
Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL.
restarts (invokable by number or by possibly-abbreviated name):
0: [ABORT] #S(RESTART
:NAME ABORT
:FUNCTION #<CLOSURE (LAMBDA #) {B2C670D}>
:REPORT-FUNCTION #<FUNCTION (LAMBDA #) {90E367D}>
:INTERACTIVE-FUNCTION NIL
:TEST-FUNCTION #<FUNCTION (LAMBDA #) {90C9E3D}>)
-bcd
--
*** Brian Downing <bdowning at lavos dot net>
Nikola Skoric <·········@net4u.hr> writes:
> It's realy lame to quote yourself, but I just forgot to ask: is there a
> way to exclude some parts of SBCL when compiling? For instance, I don't
> need CLOS right now, and every kB of disc space is of great importance
> for me...
I know you're not asking about CMUCL, so this may be irrelevant, but
you can build a CMUCL core without CLOS. If you use the "small"
feature, which byte-compiles a bunch of top level stuff, you can get a
core of about 11Mb.
--
Fred Gilham ······@csl.sri.com
Is, then, the loving cup so often filled
that we may toss a draught aside?....
-Jeff Iverson