A somewhat shalow google search doesnt give back anything
obvious, but at the same time it is hard to believe that
something like this has not been noticed previously.
The following transcript is from a FreeBSD machine. Windows
exhibits the same behaviour.
$ set | grep SBCL
SBCL_HOME=/usr/local/lib/sbcl
$ whereis sbcl
sbcl: /usr/local/bin/sbcl /usr/local/man/man1/sbcl.1.gz /usr/ports/lang/sbcl
$ sbcl --userinit /dev/null
This is SBCL 0.9.5, an implementation of ANSI Common Lisp.
[...]
* (quit)
$ /opt/bin/sbcl --core /opt/lib/sbcl/sbcl.core --userinit /dev/null
This is SBCL 0.9.4.44, an implementation of ANSI Common Lisp.
[...]
* (quit)
$ /opt/bin/sbcl --userinit /dev/null --core /opt/lib/sbcl/sbcl.core
This is SBCL 0.9.4.44, an implementation of ANSI Common Lisp.
[...]
fatal error encountered in SBCL pid 75930:
can't load .core for different runtime, sorry
The system is too badly corrupted or confused to continue at the Lisp
level. If the system had been compiled with the SB-LDB feature, we'd drop
into the LDB low-level debugger now. But there's no LDB in this build, so
we can't really do anything but just exit, sorry.
Best regards,
--
Eduardo Muñoz | (prog () 10 (print "Hello world!")
http://www.boundp.net/ | 20 (go 10))
|