Re: Avoid running non-portable testcases

[Mike Stump <MRS at apple dot com>]

On May 26, 2005, at 10:51 PM, Ziemowit Laski wrote:
> > I ran the new Objective-C testcases on linux, and found a few that  
> > seem to be non-portable, so I turned them off for now...
>
> Hmmm... shouldn't test cases be turned off iff it is determined  
> that they are not applicable to a given target, rather than merely  
> when they fail? :-)

I wanted to preserve the 0 unexpected failures for now, just to be  
conservative.  I sent out the email, so that you could decide how you  
wanted to handle it.

I noticed that the obj-c++ testsuite appears to not expose the newly  
built libobjc.so to the running app:

./method-17.exe: error in loading shared libraries: libobjc.so.1:  
cannot open shared object file: No such file or directory
FAIL: obj-c++.dg/method-17.mm execution test

:-(  So, my testing of obj-c++ on linux isn't going smoothly, plus,  
people put in some dependencies on newer tcl into the testsuite,  
which didn't help the matter.


I suspect you can grab expect and tcl out of the src repo.  The  
module names should be expect and tcl.