William Harold Newman wrote, On 6/4/08 8:46 AM:
> As far as I can see we neither have new bug reports coming in very
> fast, nor outstanding bugs likely to be fixed cleanly and promptly, so
> this looks like a reasonable candidate for bundling up and shipping.
On an Intel Mac OS X 10.5.2 (Leopard) after doing a clean build and runing the tests I get:
Invalid exit status: timer.impure.lisp
test failed, expected 104 return code, got 1
In timer.impure.lisp I see the comment:
;;;; OS X doesn't like these being at all, and gives us a SIGSEGV
;;;; instead of using the Mach expection system! Our or OS X's fault?
If this is going to be released without a fix, should it be made an expected failure?