It's also quite possible that this is part of the inherent flakiness
of the x86/darwin part at this point. I saw some sporadic contrib
failures, before I became obsessed with the underlying cause of the
x86/darwin instability.
As for the binary, I'm reluctant to let this out into the wild to
folks who aren't brave enough to do their own cross-compile until I
resolve the x86/darwin issue. Stop by #lisp for details if you're
interested. I'll try to write something about it in the next day or
so if I don't have a positive resolution, which looks tantalizingly
close yet increasingly unlikely.
Cyrus
On Mar 13, 2006, at 9:19 PM, Nikodemus Siivola wrote:
> "Li Lin" <guru.lin@...> writes:
>
>> I finally did a rebuild the whole sbcl package using make.sh on my
>> intel Mac using the sbcl excutable and core image geneated by cross
>> compiling.
>
> Uh oh.
>
> While it is certainly good to hear that yo got hings working, this
> sounds
> like we're leaking something from host to target in the build.
>
> Cheers,
>
> -- Nikodemus Schemer: "Buddha is small, clean, and
> serious."
> Lispnik: "Buddha is big, has hairy armpits, and
> laughs."
> .
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting
> language
> that extends applications into web and mobile media. Attend the
> live webcast
> and join the prime developer group breaking into this new coding
> territory!
> http://sel.as-us.falkag.net/sel?
> cmd=lnk&kid=110944&bid=241720&dat=121642
> _______________________________________________
> Sbcl-help mailing list
> Sbcl-help@...
> https://lists.sourceforge.net/lists/listinfo/sbcl-help
|