Re: trouble with distributed builds
Re: trouble with distributed builds
- Subject: Re: trouble with distributed builds
- From: Greg Guerin <email@hidden>
- Date: Mon, 27 Jul 2009 16:17:26 -0700
Stephen DiVerdi wrote:
I got the impression from the distcc faq that distcc itself doesn't
do any version checking. I also got the impression from the way
that distcc works (that hosts are specified in a file / environment
variable) that xcode uses bonjour to find hosts, check versions,
and then construct a host list to give to distcc. That implies that
xcode is doing the version checking and not distcc. But I'm having
a hard time testing any of these ideas, which is why I'm asking for
help with the troubleshooting...If the answer to that question is
really to start looking at raw ethernet traffic, then this probably
isn't worth my time. =/
Earlier versions of Xcode had a Distributed Builds pane in Xcode
Preferences that let you configure the builds, but also monitor which
Bonjour-discovered machines had the right versions. My Leopard
machine is down, and will be for a while, so I can't see what Xcode 3
has in this regard.
Here's a URL that shows the pane, and the monitoring capabilities
should be plain (Figure 6-3).
http://developer.apple.com/documentation/developertools/Conceptual/
XcodeBuildSystem/800-Reducing_Build_Times/bs_speed_up_build.html
It looks like a pretty old screen shot, though, which is why I'm
unsure what Xcode 3 has in this area.
I think the first thing to do isn't to inspect the UDP traffic (note:
not the same as "raw ethernet traffic").
The first question to answer is what version of gcc and/or distcc is
installed on the other machines. In particular, if they have not
been upgraded to the same version of Xcode as your controlling
machine, then you should at least try one experiment of upgrading one
remote machine and see if it becomes available for distcc.
Also check that nothing has disabled distcc's capabilities, such as a
possible firewall or Sharing setting becoming disabled. It might be
something simple, like the upgrade of Xcode caused its status to
change in the firewall access-control list (System Preferences,
Security, Firewall, IIRC).
The fact that a retrograde to 3.1.2 didn't change anything suggests
the problem might lie outside of Xcode itself.
-- GG
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden