Re: [gentoo-user] Difference between "normal distcc" and "distcc with pump"?

["Walter Dnes" <waltdnes@waltdnes.org>]

On Mon, May 04, 2015 at 05:29:34AM -0400, Fernando Rodriguez wrote

> All you need to do is create scripts on the host with the exact
> same names and have them execute the compiler that you want with
> the options you want (I just have it execute the 64bit compiler with
> -m32). Then make sure that distccd (on host) finds them before the
> actual compiler by putting it in the PATH environment variable before
> anything else.

  Much to my surprise, adding "-m32" to the client's CFLAGS (and
therefore also CXXFLAGS) results in seamonkey building properly.  I
tried it out on the same video, and cpu load "only" climbs to 2.5 versus
2.75 with seamonkey-bin.  The build took 1hr and 43 minutes on the Core
2 Duo host, versus 14 hours doing it on the Atom.

  Why is seamonkey the only program (so far for me) that needs "-m32"?
Would it need "-m64" if it was being cross-compiled on a 32-bit host
system for 64-bit client?  Is there a wiki that we can contribute this
info to?

-- 
Walter Dnes <waltdnes@waltdnes.org>
I don't run "desktop environments"; I run useful applications