• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: arch: posix_spawnp: /Developer/Tools/otest: Bad CPU type in executable
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: arch: posix_spawnp: /Developer/Tools/otest: Bad CPU type in executable


  • Subject: Re: arch: posix_spawnp: /Developer/Tools/otest: Bad CPU type in executable
  • From: Nick Pilch <email@hidden>
  • Date: Mon, 18 Aug 2008 09:22:17 -0700

Upgrading to Xcode 3.1 solved the problem.

On Aug 15, 2008, at 1:01 PM, Nick Pilch wrote:

Hi. I'm trying to put the infrastructure into my project for running unit tests and I'm stuck. The tests don't seem to execute. I've set things up as described here for independent tests: http://developer.apple.com/documentation/DeveloperTools/Conceptual/UnitTesting/Articles/CreatingTests.html

When trying to build/run this test I get:

arch: posix_spawnp: /Developer/Tools/otest: Bad CPU type in executable

Here's my test method:

- (void) testTest
{
	STAssertEquals(0, 1, @"Dude, 0 is not 1", nil);
}

Any help? Thanks.

_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


------------------------------------------------

Nick Pilch / Tacit Knowledge, LLC
email@hidden
Cell: 510-381-6777



_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


References: 
 >Window 'close' action fails (From: dct <email@hidden>)
 >arch: posix_spawnp: /Developer/Tools/otest: Bad CPU type in executable (From: Nick Pilch <email@hidden>)

  • Prev by Date: Re: Right place to unobserve notifications in a document
  • Next by Date: Re: Changing NSTextFieldCells' editing appearance?
  • Previous by thread: arch: posix_spawnp: /Developer/Tools/otest: Bad CPU type in executable
  • Next by thread: Re: Window 'close' action fails
  • Index(es):
    • Date
    • Thread