On Friday 08 April 2005 12:32 pm, Christophe Rhodes wrote:
> Heh, bad luck. This is in fact three separate issues, which I think
and bad timing, apparently.
> have converged on you in an unfortunate way: the removal of
> bit-bash-copy, which is notionally an internal function, affects
> builders of clx releases using an unreleased version of sbcl, which by
> now contains two separate fixes for the problem causing
> save-lisp-and-die to die without saving.
> There are several workarounds. You can replace
> sb-kernel:bit-bash-copy in clx with sb-kernel:ub1-bash-copy; you could
Are they identical in terms of args and return values, so this is
almost idiotproof (me being the idiot in question)?
> patch any of your sbcl rpms by altering (gensym "EVAL-TMP") to nil in
> src/code/eval.lisp; or you could use one of your existing cores, load
> the fasls that your previous compilation step has left lying around,
> and save a core from that. Or, you can wait until clx is likewise
> patched and released.
Given that I cannot wait, it seems that the best thing is to patch the
source to CLX (as in your first suggestion) in my .sbcl/site
And if I do patch, is there anything I can do (no matter how trivial,
like sending the single-line patch) to help expedite the fix of CLX?
What would the correct (convention-wise) '#' directive be, as a
function of SBCL implementation and release/version number?
Thanks for the prompt, bulls-eye response.
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> Sbcl-help mailing list
==== John Morrison
==== MAK Technologies Inc.
==== 10 Fawcett Street, Cambridge, MA 02138
==== vox:617-876-8085 x115