On Tue, 15 Mar 2011, William L. Thomson Jr. wrote:
Tonight I received a few questions about using distcc. Which once you
have things setup, if you want to see distcc in action. A good way to
test it out is by compiling a kernel.
make -j5 CC=distcc bzImage
or for Xen kernels
make -j5 CC=distcc
While most people don't do this, you can set your CFLAGS/CPPFLAGS
environment variables in your shell. Autoconf configure scripts will pick
up on this and add additional flags to the base flags for your
environment. I have yet to see any software package use the "-j" flag, so
that's a safe one to override. Since "-j1" is the default, you might
suddenly find all of your new compiles after you run the configure script
again to be much snappier if you increase it.
The "-j" flag specifies the number of simultaneous build processes that
are running, and multi-core CPUs will take advantage of this. So,
sometimes when you think that you are using distcc, you might actually
still be using just the cores of the local CPU if the number after the
"-j" is too small. distcc really shines when you are doing
computationally expensive compiles (high-optimization, Boost templates,
etc.).
Andrew
---------------------------------------------------------------------
Archive http://marc.info/?l=jaxlug-list&r=1&w=2
RSS Feed http://www.mail-archive.com/[email protected]/maillist.xml
Unsubscribe [email protected]
