This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Avoid running non-portable testcases



On 27 May 2005, at 12.38, Mike Stump wrote:


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.

Perhaps other maintainers can chime in here (hint, hint), but the failures you're sweeping under the carpet_are_ unexpected, until someone establishes otherwise (e.g., if they depend on some Cupertino Darwinism); therefore, I think you just let the failures be.

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.

Yeah, I'm having problems with libobjc.so and ObjC as well (see my other e-mail)...


--Zem
--------------------------------------------------------------
Ziemowit Laski                 1 Infinite Loop, MS 301-2K
Mac OS X Compiler Group        Cupertino, CA USA  95014-2083
Apple Computer, Inc.           +1.408.974.6229  Fax .5477


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]