Almost daily I sync with cvs and, in addtion to bootstapping with sbcl
itself, I try to cross compile sbcl with clisp (the win32 version, not
the cygwin version). Every so often I'll sync to a revision that always
blows up with something similair to the attached error.
Matthew Swank <akopa@...> writes:
> Any ideas?
There is something that is either a bug in SBCL's cross-compiler or a
bug in CLISP that causes a miscompilation of some kind. Altering the
system to produce the same binary fasl files every time (i.e. not
including details such as the date and time in debug information)
would probably help to track down the problem.