[Bug 433228] Review Request: distcc - Distributed C/C++ compilation

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: Review Request: distcc - Distributed C/C++ compilation


https://bugzilla.redhat.com/show_bug.cgi?id=433228


denis at poolshark.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |lpoetter at redhat.com




------- Additional Comments From denis at poolshark.org  2008-02-22 06:16 EST -------
icecream integration: so icecream offers a similar service to distcc, and
enables the service automatically by using a ccache-style file in profile.d. To
be honest, I cringe in horror when I look at /etc/profile.d/icecream.sh: it
manually check for the presence of ccache and changes its path order
accordingly. How can that possibly scale when more and more projects want to
provide a gcc alternative ? I guess that would be a would debate to have on
fedora-devel or on the packaging committee (assuming it didn't happen already).
So if you have both distcc and icecream installed, and if you use distcc the old
fashioned way with "make CC=distcc", distcc will be called first, but builds
scheduled to localhost will then invoke icecream, which will fall back to
localhost again or go remote if icecream is configured. So it will work of
course, but may confuse some people if you actually configured both servicess.

About Lennart's avahi patch: Lennart I had some issues with your patch: it
touches both "configure" and "configure.ac", and a Makefile.in change references
a file "distccmon-gnome.1" that's not part of the tarball and causing "make
install" to fail. I massaged the patch to make it build and gave the feature a
try on a virtual machine. Unfortunately I was unable to make it work. distccd
starts correctly with --zeroconf (although the verbose log mentions nothing
about avahi service being enabled?), but I'm seeing this ominous message on the
client system when I start distccd:

Feb 22 11:54:27 jupiler avahi-daemon[30737]: Invalid legacy unicast query packet.
Feb 22 11:54:28 jupiler avahi-daemon[30737]:last message repeated 2 times

(server and client systems run F-8).

Any thoughts ? 


-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.