Talk:Distcc

Distcc standard used TCP/IP port

in the topic "Add port numbers to DISTCC_HOSTS on the i686 chroot" they talk about a predefined port being "3692".

It was defined nowhere, and its not the standard TCP port, which can create alot of confustion.

For those of you who use firewalls, the standard used TCP port is 3632, not 3692 (the only port being mentioned in this article) .

—This unsigned comment is by Eggz (talk) 12:28, 3 December 2017‎. Please sign your posts with ~~~~!

@Eggz - As you noted, this is under the cross-compiling for another arch section... one uses a non-standard port to allow for parallel operation of x86_64 and i686 if needed. Using 3632 in both would result in a failure if both services were running simultaneously. You also want to sign you posts by typing four tildes. Graysky (talk) 12:34, 3 December 2017 (UTC)

Compiling with default Arch CFLAGS

Current Arch default CFLAGS/CXXFLAGS are -march=x86-64 -mtune=generic -O2 -pipe -fno-plt. Though it is explicitly stated that native shouldn't be used at all, what about generic optimizations?

Dviktor (talk) 09:14, 11 November 2019 (UTC)!

You should be fine passing -mtune=generic or any other (see man gcc) values. As I understand things, it is just the native march target causes problems. Graysky (talk) 12:59, 11 November 2019 (UTC)

distccmon-gnome

gtk monitor distccmon-gnome is not longer included in the distcc package?

Bronze (talk) 04:12, 27 December 2020 (UTC)

Looks like it was dropped with the 3.3.3-8 release. Graysky (talk) 12:08, 27 December 2020 (UTC)

I can update section 5 of the wiki with "distccmon-gnome was included at least in distcc-3.3.3-7"? Bronze (talk) 15:42, 27 December 2020 (UTC)

Of course, it's a wiki after all. I would just delete the text. No point in advertising a feature that does not exist in our package. Graysky (talk) 16:51, 27 December 2020 (UTC)