Tuesday, July 26, 2005
SBCL 0.9.3 RPMs released
The RPMs for 0.9.3 are up on SourceForge. Amazingly, I actually had time to get this stuff done on the day the sources were released. Enjoy!
Comments:
Hi Dave,
When I built the 0.9.2.x series on Fedora Core 4, I found that it was extremely unstable with threads. It turns out that gcc4 does not work properly for compiling SBCL, but gcc32 does. What gcc did you use for the RPM?
Right now, I'm building the RPMs on Fedora Core 3. Currently, I'm using GCC 3.4.3, specifically the gcc-3.4.3-22.fc3 version RPM.
Hey Dave. I have a quick question for you. I'm getting an error (internal error #29) periodically when sbcl first starts up on Fedora Core 3 with your build. (Was getting it with my own build as well...) Just wondering if you're getting the same thing or if it might be something on my end. This happens maybe 40% of the time when sbcl is started. It occurs regardless of whether I do:
$ sbcl
or
$ setarch i386 sbcl
Thanks!
Sorry Dave. Figured out my problem. At first I thought that I would try "setarch i386 sbcl" according to the docs and when that didn't work out I wasn't sure what to do. I just read in a mailing list that you need to disable randomizing addressing in the kernel (part of SELinux?):
$echo 0 > \
/proc/sys/kernel/randomize_va_space
Didn't find this in any of the docs (at least not where I looked) Hopefully this helps anybody else who is having simmilar problems.
Post a Comment
Hi Dave,
When I built the 0.9.2.x series on Fedora Core 4, I found that it was extremely unstable with threads. It turns out that gcc4 does not work properly for compiling SBCL, but gcc32 does. What gcc did you use for the RPM?
Right now, I'm building the RPMs on Fedora Core 3. Currently, I'm using GCC 3.4.3, specifically the gcc-3.4.3-22.fc3 version RPM.
Hey Dave. I have a quick question for you. I'm getting an error (internal error #29) periodically when sbcl first starts up on Fedora Core 3 with your build. (Was getting it with my own build as well...) Just wondering if you're getting the same thing or if it might be something on my end. This happens maybe 40% of the time when sbcl is started. It occurs regardless of whether I do:
$ sbcl
or
$ setarch i386 sbcl
Thanks!
Sorry Dave. Figured out my problem. At first I thought that I would try "setarch i386 sbcl" according to the docs and when that didn't work out I wasn't sure what to do. I just read in a mailing list that you need to disable randomizing addressing in the kernel (part of SELinux?):
$echo 0 > \
/proc/sys/kernel/randomize_va_space
Didn't find this in any of the docs (at least not where I looked) Hopefully this helps anybody else who is having simmilar problems.
Post a Comment
Links to this post: