Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Need help with 'unable to open executable ... ' error

After I compile I get this error. Here is the entire error msg:
==

error: unable to open executable '/Users/..MyName../Library/Developer/Xcode/DerivedData/BallsAway-dxopkhiuo..... .zemqfcgnldx/Build/Products/Debug-iphonesimulator/BallsAway.app/BallsAway'


This a brand new Xcode project so I am not sure what the issue is. Any suggestions or comments will be greatly appreciated.

Thanks.

24" iMac, 17" i7 MacBook Pro, iPhone 4, Mac OS X (10.6.7)

Posted on Apr 1, 2011 6:57 AM

Reply
11 replies

Apr 1, 2011 8:09 AM in response to Phillip Anthony

In looking at the path noted above, I have discovered that the BallsAway.app folder does not even exist. the BallsAway icon is in the Debug-iphonesimulator folder.

Further, getting Info on the app icon reveals that it is only 8K in size, which makes no sense.

I have also noticed that the executable file (in the app folder structure) is in red ink meaning that it is missing.

Why would Xcode4 not create an executable app file?

Thanks.

Apr 1, 2011 10:11 AM in response to Phillip Anthony

I just Repaired Perms again, and I always see tons of references to Java in the DU log. I always see these references. I am using latest OS X, so do not understand the problem.

Anyway, some of the apps that would not launch in Xcode4 now do launch, but the executable app file is still red, meaning they are not being built.

So, I am still at square one with this problem.

Apr 1, 2011 3:50 PM in response to xnav

I've spent most of the day doing a lot of investigation. Results of that are:

With regard to Xcode4:
What would not run properly yesterday, did run fine today.
Background: I have used DU to Repair Perms twice today. I have always seen lots of references to Java and frameworks in the DU log while doing this. Whether there is a correlation or not to my problems, I do not know.

With regard to Xcode v325:
I can now run apps that had previous compile errors with no problems and so on.

Then a few hours ago, I was running Xcode4 and doing fine until I tried to again run the app on the iP4 and it refused to run. It all of a sudden developed the Info.plist problem again.

I switched back to Xcode 325 and it ran fine. I'm not ready to really point ALL of the blame on Xcode 4, because Apple doc's state clearly that user's can switch back and forth between versions without problems. I'm not so sure. I am not switching back and forth because I think it's a fun thing to do, I'm doing it because I have no other choice.

As to the red fonted files - from my experience, that means either the file is nowhere to be found or it has not been built, which I think was my original problem. I have no idea how to correct that. Earlier today I had a sit where the app actually ran on the sim even though the executable was in red font. I have no idea how that works either.

At the moment, I'm using Xcode v325 and doing OK. I may download the latest Xcode 4 upgrade tonight. Not sure yet.

Thanks for checking in.

Sep 20, 2011 4:02 AM in response to EricFromAarhus

I found the solution to my problem with "error: unable to open executable" in Xcode 4.

I had been using the -M option for GCC which suppressed the warnings that would have told me why no executable file had been created. Once I removed -M, a different set of errors led me to include a library I had been missing. Once that library was added, the build succeded!

Need help with 'unable to open executable ... ' error

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.