arm-apple-darwin9-gcc-4.0.1: No such file or directory

Question

arm-apple-darwin9-gcc-4.0.1: No such file or directory

Clean-install of Xcode3.0 followed by iPhone SDK beta 6. Both installs succeed without any errors or warnings. Freshly created project compiles fine for simulator, but when I attempt to compile for device I get this error sequence for every file that needs compilation:

-----

gcc-4.0: installation problem, cannot exec '/Developer/usr/bin/arm-apple-darwin9-gcc-4.0.1': No such file or directory

distcc[477] ERROR: compile /Volumes/WorkHD/Projects/iPhoneStuff/iphoneapp1/Classes/RootViewController.m on localhost failed with exit code 255

Command /Developer/usr/bin/distcc failed with exit code 255

-----

The odd thing here is that I've now completely uninstalled and reinstalled both Xcode3 and the iPhone SDK 6 a few times, and always receive the same errors. It's as if it isn't properly picking up that it needs to look in ...iPhoneOS.platform/Developer/usr/bin for the arm compiler tools. Yet all that setup should have been done as part of the iPhone SDK installation, no?

Anyone?

Message was edited by: John F Wiederhirn

Mac Pro (2x2.66 Dual Xeon), Mac OS X (10.5.3), 6GB Ram, ATI X1900XT

Posted on Jun 7, 2008 8:51 PM

Reply

Answer 1

Clea Rees

Level 4

1,245 points

Jun 8, 2008 10:01 AM in response to John F Wiederhirn

Are you setting the system root appropriately?

Does anything in this thread help?

- cfr

Reply

Answer 2

Jun 8, 2008 11:25 AM in response to Clea Rees

I actually suspect that's precisely the problem. Unfortunately, I'm trying to do this entirely within Xcode 3.1, and setting -Isysroot in CFLAGS in the build settings didn't help, nor did putting the platform .../usr/bin manually in the path.

Xcode seems to have a pre-configured notion that the arm-apple-darwin9... stuff lives in /Developer/usr/bin (see error text) and I can't find any settings which let me explicitly revise the system root in a way that also impacts where it looks for the tools (compilers, etc.) themselves.

I've now tried the clean-install of Xcode3 & SDK5 as well, with the same results. I'm slowly working backwards to see where Device builds stopped worked (or if it ever worked -- I focused mostly on the simulator early on). That said, if someone knows the missing fix (using the Xcode UI), I'd much prefer to just get working again, instead of playing "reductio ad nauseum".

Message was edited by: John F Wiederhirn

Reply

Answer 3

Jun 8, 2008 12:40 PM in response to John F Wiederhirn

Okay, so after a bit more research, here's what I've found (all starting from clean-installs):

Xcode3 + iPhone SDK 4 (2165) == *+working Device builds+*
Xcode3 + iPhone SDK 4 (2165) + SDK 6 (2192) == broken Device builds (compiler not found)
Xcode3 + iPhone SDK 5 (2173) == broken Device builds (compiler not found)
Xcode3 + iPhone SDK 6 (2192) == broken Device builds (compiler not found)

So clearly something in the SDK 5 & 6 installs changed from SDK 4, and as a result appears to have broken Device builds (at least on my system).

I guess I'll revert to SDK 4 and try to continue, and send my results to Apple as a bug. If anyone out there knows how to fix this inside Xcode, I'd really like to know.

Reply

Answer 4

Jun 11, 2008 4:54 PM in response to John F Wiederhirn

And with the notes from SDK beta 7, the answer is revealed: I was running into the distcc problem mentioned in the notes.

Back to work!

Reply

Answer 5

Jul 14, 2008 6:53 AM in response to John F Wiederhirn

Hi John, I don't have SDK beta7 (just the latest 'final'), and I have this problem too! Could you help please? Thanks 🙂

Reply

Answer 6

Jul 15, 2008 4:45 AM in response to John F Wiederhirn

Can anyone help with this? I'm *completely stuck* and can't find the release notes for SDK 7, even though I managed to get a copy of it - I guess the release notes must have been online but are now removed!

Reply

Answer 7

Jul 21, 2008 12:08 PM in response to tenzarelli

The solution to this problem is to go to xCode...Preferences...Distributed Builds, click the lock to make changes, check the "Share my computer for shared workgroup builds", click Apply, then uncheck that same box and click Apply again. Worked for me, hope it works for you.

Reply

Answer 8

flod

Level 1

0 points

Aug 30, 2008 2:48 PM in response to tenzarelli

I second this.
On the final SDK it worked for a few builds, than these errors pop up.
I didn't touch any build flags and checking /Developer/usr/bin really shows those files missing.
For a quick solution I've sym-linked the arm*-4.0.1 from the Platforms directory (where they seem to be installed), but I'm not sure this won't introduce problems in the future.
Has anyone any idea what might have happened, or some proper solution for fixing this?
Thanks!

Reply

Answer 9

Aug 30, 2008 5:53 PM in response to John F Wiederhirn

I just noticed this same problem when I have distributed builds set. Go into prefs->distributed builds and uncheck distribute via. It should now compile for the device.

Weirdly, it will do a distributed build for the simulator, just not for the device (because the arm compilers are in the wrong place).

Reply

Answer 10

Feb 10, 2009 9:18 PM in response to Maverick808

thanks Maverik your trick work !!!!

after hours of tedious blog searching u gave me the solution. thnaks!

Teo

Reply

Answer 11

ijoey

Level 1

0 points

Jul 2, 2009 12:21 PM in response to John F Wiederhirn

I have this problem too using SDK 3. The compiler is trying to find /Developer/usr/bin/arm-apple-darwin9-gcc-4.0.1 and it's not there. It's in /Developer/Platforms/iPhoneOS.platform/Developer/usr/bin/. What gives?

Reply

Answer 12

ijoey

Level 1

0 points

Jul 2, 2009 2:10 PM in response to John F Wiederhirn

I've found the culprit in my environment. Here's what I have:

iPhone SDK 3.0
Xcode 3.1.3
Mac Mini 10.5.7
Target iPhone OS 2.2.1 for Device

I had Distributed Builds turned on, Distribute via Shared workgroup build (distcc) checked. As soon as I deselected "Distribute via" in Xcode preferences Distributed Builds, everything compiled correctly. I hope this helps others.

Reply