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 That will definitely use distcc, and it will let you know on command line if it can't. It will spit out fail to distribute to "" running locally. From there you can use distccmon, and/or htop/top to monitor and see distcc/cc process on the other machines/distcc nodes. The one thing I have not done with distcc thats been on my list for years is cross compiling. So my x86 machines can use my amd64 machines to compile and vice versa :) Unfortunately not to many packages build systems support parallel compiling or make file invocations. Which if thats the case usually the Gentoo ebuild will have the make options hard set to -j1. But same applies to any package you build from source manually. Now I am not sure about using distcc only as your compiler. I am not sure if an entire package can be compiled using a remote compiler and not using the local one at all. Need to run some tests/experiments and find out. -- William L. Thomson Jr. Obsidian-Studios, Inc. http://www.obsidian-studios.com --------------------------------------------------------------------- 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]
