"Elliott Slaughter" <elliottslaughter@...> writes:
> On Sun, May 18, 2008 at 2:58 AM, Nikodemus Siivola
> <nikodemus@...> wrote:
>> On Sun, May 18, 2008 at 2:54 AM, Elliott Slaughter
>> <elliottslaughter@...> wrote:
>>> Unfortunately it still seems to be broken (stops right after compiling
>>> ; compiling file
>>> (written 14 JUL 2005 09:30:14 AM):
>>> [... compilation of file seems to complete (with warnings) ...]
>>> ; C:\Bin\MSYS1.0\sbcl-184.108.40.206\obj\from-host\src\code\cross-make-load-form.lisp-obj-tmp
>>> ; compilation finished in 0:00:00
>>> debugger invoked on a SIMPLE-ERROR:
>>> FAILURE-P was set when creating
>> The important bits are the "caught WARNING" and "caught ERROR"
>> messages earlier in the scrollback. FAILURE-P here means that
>> COMPILE-FILE returned a tertiary return value of true.
> Here are the warnings immediately before what I posted previously.
> (There are style warnings before this, but since they seem to be even
> distributed throughout the build I didn't want to post too much. Let
> me know if you would like more.)
> ; compiling file
> (written 14 JUL 2005 09:30:14 AM):
> ; compiling (IN-PACKAGE "SB!INT");
> ; caught WARNING:
> ; Found non-STANDARD-CHAR in "MAKE-LOAD-FORM-SAVING-SLOTS ~
> ; called with :SLOT-NAMES argument during cross-compilation"
I think you've probably checked out this copy of SBCL with the Windows
line-ending convention. While that's a sensible enough thing to do,
one of the things SBCL doesn't currently support is end-of-line
convention handling, so you get a literal #\Return in that string,
which won't work. SBCL's build process defends against that early
rather than late.
There's some kind of argument to cvs, I believe, which tells it not to
convert newlines for text file checkouts; you'll need to use that.