Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
From: Andrey G. Grozin <A.G.G<rozin@in...> - 2009-03-28 14:51:27
I maintain maxima package in Gentoo Linux. maxima can be compiled by
several lisps; sbcl seems now most popular. I got a bug report from a user
trying to compile maxima with sbcl on a 64-bit Intel. When he runs make
(after configuring maxima to use sbcl), make calls
sbcl --noinform --noprint --eval (progn (load
"../lisp-utils/defsystem.lisp") (funcall (intern (symbol-name
:operate-on-system) :mk) "maxima" :compile :verbose t) (sb-ext:quit))
sbcl tries to re-write the files
/usr/lib64/sbcl/sb-grovel/defpackage.fasl, def-to-lisp.fasl and
foreign-glue.fasl (these files were originally installed by the sbcl
package, currently 1.0.26). Package compilations in gentoo are performed
in a sandbox, writing outside this sandbox is not allowed, and make fails.
I don't have this problem on my 32-bit Intel box running Gentoo.
So, my question is: under what circumstances will sbcl want to re-generate
fasl files in sb-grovel? Maybe, something is wrong with the Gentoo sbcl
package; if so, I'll contact its maintainer.
P.S. I have a very positive experience with sbcl developers: when I had
problems with compiling maxima on 64-bit SUSE Linux, the developers were
very helpful, and found and fixed the bug really quickly. Many thanks in