Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
Thiemo Seufer <ths@...> writes:
>> I had a closer look and found a lot more bugs than expected. The
>> resulting diff against CVS HEAD is >50k and improves stability of
>> the mips port significantly. I'll split it in pieces and add a short
>> explanation to each.
Thank you very much for all of this. I believe I have now merged them
all except for the one in the message I'm replying to, regarding...
> Ignore tests which currently fail on mips. foreign.test.sh is the
> odd one out, mips falls in the debugger, I haven't had a closer look
... tests which fail. I don't like this, because the tests lose their
documenting and nagging nature in this case. On the other hand, if
this is what is required for Peter's debian package, that's fine, and
he can track mainline but with tests deactivated.
> The stat-related test failures in contrib/posix are most likely
> caused by a inconsistent structure definition which doesn't match
> the one used by linux/mips. There's probably a way to automatically
> extract it from /usr/include/bits/stat.h, but that's not done in the
> current implementation.
It is meant to be done: contrib/sb-posix/constants.lisp is processed
by sb-grovel, emitting contrib/sb-posix/constants.lisp-tmp which is
then processed as a lisp file. sb-grovel is meant to use the C
compiler to grovel a machine-specific structure, and stat is one such
that we ask for: see alien-stat in contrib/sb-posix/constants.lisp.
Is the status now that, apart from these failing tests, the mips/linux
(and mipsel/linux) builds are expected to work?