[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: gnustep-base-1.5.2 test on solaris2.7
|
From: |
Richard Frith-Macdonald |
|
Subject: |
Re: gnustep-base-1.5.2 test on solaris2.7 |
|
Date: |
Thu, 13 Mar 2003 19:47:58 +0000 |
On Thursday, March 13, 2003, at 06:05 pm,
bug-gnustep-bounces+richard=brainstorm.co.uk@gnu.org wrote:
I tested gnustep-*-1.5.2 on a few systems. Please don't release 1.6.0
yet,
because 1.5.2 does not install on darwin (gnu-gnu-gnu) out of the box!
But does the 1.6.0 cvs branch?
Most of the tests in subdirectory Testing work, nsconnection allows
sending (and receiving) structs to ix86-linux, only nsdata fails:
obj/nsdata: Uncaught exception NSMallocException, reason: Unable to
create
shared memory segment - Invalid argument.
Possibly solaris limits the size of shared memory segment you can
create?
I updated the 1.6.0 branch to report the size that it was trying to use
in the exception,
but the test is trying for 2000000 bytes.
Could somebody review the tests: Some don't compile (nsdate), some seem
quite buggy (nsbundle, nsbasic, nstimezone), some don't "talk"
(nsfilemanager) and some I simply don't understand (call, string,...)
That would be nice ... I don't think anyone uses the files in the
Testing directory
much, perhaps we should remove some.
I finally run the gnustep-tests-1.4.0:
For testing the 1.6.0 branch prior to 1.6.0 release, using the tests
from CVS would probably be best.
On debian/intel I get 2552 expected passes, and 2 expected failures.
The results are attached
To run them, I had to install guile (NOT the recommended version 1.6,
this
should be changed to 1.4.1),
Yes ... unless we can update to support 1.6 (I think someone did some
work on that,
but I can't recall what happened to it).
and gnustep-guile, which at the moment
doesn't compile without changes (link_base.m)
Worked for me ... current CVS
Why does it fail for you?
XML is not installed, that's why a few tests fail. Tell me, if it's
absolutely necessary to do tests with XML.
For Apple/MacOS-X compatibility, XML support is needed (Apple property
lists are XML).
If you don't want apple compatibility, it's an optional extra.