Contents of /xml/htdocs/doc/en/distcc.xml

Parent Directory Parent Directory | Revision Log Revision Log

Revision 1.9 - (hide annotations) (download) (as text)
Sun Oct 12 17:38:25 2003 UTC (15 years ago) by swift
Branch: MAIN
Changes since 1.8: +4 -4 lines
File MIME type: application/xml
Fix 30969

1 swift 1.1 <?xml version='1.0' encoding="UTF-8"?>
2 blubber 1.3 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
3 swift 1.9 <!-- $Header: /home/cvsroot/gentoo/xml/htdocs/doc/en/distcc.xml,v 1.8 2003/10/11 17:21:58 swift Exp $ -->
4 blubber 1.2
5 swift 1.1 <guide link="/doc/en/distcc.xml">
7     <title>Gentoo Distcc Documentation</title>
9     <author title="Author">
10 erwin 1.4 <mail link="lisa@gentoo.org">Lisa Seelye</mail>
11     </author>
13     <author title="Editor">
14     <mail link="vapier@gentoo.org">Mike Frysinger</mail>
15     </author>
17     <author title="Editor">
18     <mail link="erwin@gentoo.org">Erwin</mail>
19 blubber 1.2 </author>
21     <author title="Reviewer">
22 erwin 1.4 <mail link="swift@gentoo.org">Sven Vermeulen</mail>
23 swift 1.1 </author>
24 blubber 1.2
25 swift 1.1 <author title="Reviewer">
26 erwin 1.4 <mail link="blubber@gentoo.org">Tiemo Kieft</mail>
27 swift 1.1 </author>
29 swift 1.6 <license/>
31 swift 1.9 <version>1.2.4</version>
32     <date>October 12, 2003</date>
33 swift 1.1
34 blubber 1.2 <abstract>This document serves as a HOWTO for using distcc with Gentoo.</abstract>
35 swift 1.1
36     <chapter>
37 blubber 1.2 <title>Introduction</title>
38     <section>
39     <title>What is distcc?</title>
40     <body>
41     <p>Distcc is a program designed to distribute compiling tasks across a network to participating hosts. It is comprised of a server, <c>distccd</c> and a client program, <c>distcc</c>. Distcc can work transparently with <uri link="http://ccache.samba.org">ccache</uri> and Portage with a little set up.</p>
42     </body>
43     </section>
44 swift 1.8 </chapter>
46     <chapter>
47     <title>Setup</title>
48 blubber 1.2 <section>
49 erwin 1.4 <title>Dependencies</title>
50 blubber 1.2 <body>
51 swift 1.8 <pre caption="Distcc dependencies (2.8 through 2.10)">
52 swift 1.1 &gt;=sys-apps/portage-2.0.46-r11
53 swift 1.8 <codenote>Distcc-2.11 and on require &gt;=sys-apps/portage-2.0.49-r6</codenote>
54 swift 1.1 &gt;=sys-devel/gcc-config-1.3.1
55 erwin 1.4 sys-apps/shadow
56 swift 1.8 <codenote>(As of version 2.8 and up until 2.11) And the following optional dependencies when you have <i>gtk</i> in your <i>USE</i> flags</codenote>
57 swift 1.1 &gt;=x11-libs/gtk+-2.2.1
58 swift 1.8 </pre>
59     <pre caption="Distcc Dependencies (post 2.11.1)">
60     &gt;=sys-apps/portage-2.0.49-r6
61     &gt;=sys-devel/gcc-config-1.3.1
62     sys-apps/shadow
63     <codenote>In this revision you may chose between a Gnome and GTK GUI monitor, they have the following added dependencies</codenote>
64     <codenote>For GTK:</codenote>
65     &gt;=x11-libs/gtk+-2.0.0
66     &gt;=gnome-base/libglade-2.0.0
67     x11-libs/pango
68     <codenote>For Gnome:</codenote>
69     &gt;=x11-libs/gtk+-2.0.0
70     &gt;=gnome-base/libglade-2.0.0
71     x11-libs/pango
72     &gt;=gnome-base/libgnomeui-
73     &gt;=gnome-base/libgnome-2.0.0
74     </pre>
75     </body>
76     </section>
77     <section>
78     <title>Installing Distcc</title>
79     <body>
80     <p>Installing Distcc is very easy. Simply set your USE flags and <i>emerge distcc</i>. But, there's a couple of options you should know about.</p>
81     <p>Distcc ships with a graphical monitor to monitor tasks that your computer is sending away for compilation. If you use Gnome then put 'gnome' in your USE flags. However, if you don't use Gnome and would still like to have the monitor then you should put 'gtk' in your USE flags.</p>
82 blubber 1.2 </body>
83     </section>
84     <section>
85     <title>Setting up Portage to use Distcc</title>
86     <body>
87     <p>Setting up distcc is very easy to do with Portage. Follow these simple steps on each computer you want to use distcc on:</p>
88     <pre caption="Integrating Distcc and Portage">
89 swift 1.1 # <i>emerge distcc</i>
90     # <i>nano -w /etc/make.conf</i>
91 swift 1.5 </pre>
92 swift 1.8 <impo>If you use distcc-2.11.1 or greater with &gt;=portage-2.0.49-r6, then all you need to do as far as setup is to set your hosts (see next code block), modify MAKEOPTS in <path>/etc/make.conf</path>, and add 'distcc' to FEATURES in <path>/etc/make.conf</path>.</impo>
93 swift 1.5 <note>Edit your FEATURES flags to include &quot;distcc&quot;</note>
94 swift 1.9 <note>You should also uncomment the PORTAGE_TMPDIR line in <path>/etc/make.conf</path>.</note>
95 swift 1.8 <note>Set <i>DISTCC_DIR=${PORTAGE_TMPDIR}/portage/.distcc</i> near the end of the file (last line is okay)</note>
96 swift 1.1
97 erwin 1.4 <p>Next you have to specify what hosts you want to use. To do this you can use the <c>distcc-config</c> command to set the list of hosts. Here is an example of some hosts that might be in your list:</p>
98 blubber 1.2 <pre caption="Examples of host definitions">
99 swift 1.8
102     @ @
103     </pre>
104 erwin 1.4 <p>It may all look complicated, but in most cases a variant of line 1 or 2 will work. An explanation of each line is: Line 1 is just a space-delimited list of hosts that will use default everything. Line 2 is a list of hosts that specifies the maximum number of jobs (by use of the /N) to send that host at any given time (specified with the <c>/n</c>). Since most people won't be using lines 3 or 4, I'll <uri link="http://distcc.samba.org/man/distcc_1.html">point you to</uri> the distcc docs for more information.</p>
105 blubber 1.2 <p>A sample command to set the hosts (for line 1) is:</p>
106     <pre caption="Sample command to set the hosts">
107 erwin 1.4 # <i>/usr/bin/distcc-config --set-hosts ""</i>
108 swift 1.8 </pre>
109 swift 1.1
110 swift 1.5 <p>The final step to integrating distcc into Portage is to re-open your <path>/etc/make.conf</path> and edit <c>MAKEOPTS</c> to include <c>-jN</c> (where N is an integer). Typically you will want to set this to the total number of processors in your network plus one.</p>
111 blubber 1.2 <pre caption="Final steps in make.conf">
112 swift 1.1 # <i>nano -w /etc/make.conf</i>
113 swift 1.5 MAKEOPTS=-jN
114 swift 1.8 </pre>
115 swift 1.5 <impo>Don't forget to start the distcc daemon! <c>/etc/init.d/distccd start</c></impo>
116 blubber 1.2 </body>
117     </section>
118     <section>
119     <title>Setting up Distcc to Work With Automake</title>
120     <body>
121 swift 1.8 <p>This is in some cases easier than the Portage setup. What you have to do is update your <c>PATH</c> environmental variable to include <path>/usr/lib/distcc/bin</path> before where gcc (<path>/usr/bin</path>). However, there is a caveat. If you use ccache you have to put distcc after the ccache part. Like so:</p>
122 blubber 1.2 <pre caption="Setting your path">
123 swift 1.1 # <i>export PATH="/usr/lib/ccache/bin:/usr/lib/distcc/bin:${PATH}"</i>
124 swift 1.8 </pre>
125     <p>Then, as you would normally type <c>make</c>, you would type <c>make -jN</c> (where N is an integer). A safe number to use for N varies on your network and the types of computers you are using to compile. For me, I have a dual processor P3 and a K6-2/400 that compile everything for my desktop (a 1200MHz Athlon Thunderbird) and I use -j5. Test your own settings to find the right number.</p>
126 blubber 1.2 </body>
127     </section>
128     </chapter>
129 swift 1.1
130 blubber 1.2 <chapter>
131     <title>Cross-Compiling</title>
132     <section>
133     <title>A Note on Cross-Compiling</title>
134     <body>
135     <p>Cross-compiling is using one architecture to build programs for another architecture. This can be as simple as using an Athlon (i686) to build a program for a K6-2 (i586), or using a Sparc to build a program for a ppc.</p>
136     </body>
137     </section>
138     <section>
139     <title>A Personal Note on Cross-compiling</title>
140     <body>
141     <p>I'd love to be able to help out on the Gentoo Cross-compiling effort, but I don't have any non-x86 machines. I can create things that work <e>in theory</e>, but I have to rely on other people to test what I write. That works to an extent, but it's tough. ;-)</p>
142     <p>In the near future I hope to acquire a Sparc of some type to put Gentoo on so I can play around in-house.</p>
143     </body>
144     </section>
145 swift 1.1 </chapter>
147     <chapter>
148 blubber 1.2 <title>Using Distcc to Bootstrap</title>
149     <section>
150 swift 1.8 <title>Step 1: Setup on New Box</title>
151 blubber 1.2 <body>
152 erwin 1.4 <p>Next, you have to boot your new box with a Gentoo Linux LiveCD and follow all of the steps up until the bootstrapping. Then proceed with a little preliminary setup on the new box.</p>
153 blubber 1.2 <pre caption="Preliminary Setup">
154     <codenote>Here we add distcc to FEATURES</codenote>
155 swift 1.8 # <i>nano -w /etc/make.conf</i>
156     <codenote>Add &quot;distcc&quot; to FEATURES</codenote>
157     <codenote>Modify MAKEOPTS in <path>/etc/make.conf to include -jN (as described above)</path></codenote>
158     </pre>
159 erwin 1.4 <p>Then add the distcc user to your <path>/etc/passwd</path>:</p>
160 blubber 1.2 <pre caption="Add the distcc user to /etc/passwd">
161 swift 1.5 # <i>echo "distcc:x:240:2:distccd:/dev/null:/bin/false" &gt;&gt;/etc/passwd</i>
162 erwin 1.4 <codenote>Do not forget the `<i>&gt;&gt;</i>'</codenote>
163 swift 1.8 </pre>
164 blubber 1.2 </body>
165     </section>
166     <section>
167 swift 1.8 <title>Step 2: Getting Distcc</title>
168 blubber 1.2 <body>
169 swift 1.8 <p>Next you will want to issue the following command inside the chroot on the new box.</p>
170     <pre caption="Getting Distcc on the new box">
171     # <i>emerge --nodeps distcc</i>
172     </pre>
173 blubber 1.2 </body>
174     </section>
175     <section>
176 swift 1.8 <title>Step 3: Setting Up Distcc Itself</title>
177 blubber 1.2 <body>
178     <p>Now set up distcc itself...</p>
179     <pre caption="Final distcc setup">
180 erwin 1.4 # <i>/usr/bin/distcc-config --install</i>
181     # <i>/usr/bin/distcc-config --set-hosts "localhost host1 host2 host3 ..."</i>
182 swift 1.8 </pre>
183 erwin 1.4 <p>distcc should be set up now to bootstrap! Continue the official install guide, and don't forget to re-emerge distcc after <c>emerge system</c>.</p>
184 blubber 1.2 </body>
185     </section>
186     </chapter>
187 swift 1.1
188 swift 1.5 <chapter>
189 swift 1.8 <title>Troubleshooting</title>
190 swift 1.5 <section>
191     <title>Mozilla and Xfree</title>
192     <body>
193     <p>As you emerge various packages, you'll notice that they aren't being distributed (and indeed aren't being built in parallel). This is because the developers of Mozilla and Xfree .ebuilds disabled parallel building because it is known to cause problems. This isn't necessarily a distcc problem.</p>
194     <p>That isn't to say that sometimes distcc will cause a package to fail to compile.</p>
195     </body>
196     </section>
197     <section>
198     <title>A Mixture of hardened-gcc and non-hardened-gcc Hosts Will Be Faulty</title>
199     <body>
200     <p>With such a long title any explanation here is almost irrelevent. However, if you plan to use distcc across hosts that have the <uri link="http://www.gentoo.org/proj/en/hardened/etdyn-ssp.xml">PaX/hardened-gcc</uri> and some that do not, you will run into problems.</p>
201     <p>The solution requires a little foresight on your part; you have to run <c>hardened-gcc -R</c> on the host that has PaX/hardened-gcc, or you have to enable PaX protections in your kernel and <c>emerge hardened-gcc</c>. Both of which are a good thing to do since for the most part the protections offered by both packages is a good thing and is transparent to the user.</p>
202     </body>
203     </section>
204     <section>
205     <title>Mixed GCC Versions</title>
206     <body>
207     <p>If you have differing versions of GCC on your hosts, there will likely be very weird problems. The solution is to make certain all hosts have the same GCC version.</p>
208     </body>
209     </section>
210     </chapter>
211 swift 1.1
212     <chapter>
213 blubber 1.2 <title>Distcc Extras</title>
214     <section>
215     <title>Distcc Monitors</title>
216     <body>
217     <p>Distcc ships with two monitors. The text-based one is always built, it is called <c>distccmon-text</c>. Running it for the first time can be a bit confusing, but it is really quite easy to use. If you run the program with no parameter it will run once. However, if you pass it a number it will update every N seconds, where N is the argument you passed.</p>
218 swift 1.8 <p>The other monitor is only turned on if you enabled <c>gtk</c> or <c>gnome</c> in your <c>USE</c> flags. This one is GTK+ based and runs in an X environment, and it is quite lovely.</p>
219 blubber 1.2 <p>There is a caveat to using these programs. If you want to monitor any emerge, you have to start the monitor like so:</p>
220     <pre caption="Starting the monitors">
221 swift 1.8 # <i>DISTCC_DIR=/path/to/distccdir distccmon-text N</i>
222 swift 1.1 <codenote>Or you can start the graphical monitor...</codenote>
223 swift 1.8 # <i>DISTCC_DIR=/path/to/distccdir distccmon-gnome</i>
224     </pre>
225     <impo>If you are using Portage and used the above example, this will be <c>DISTCC_DIR=/var/tmp/portage/.distcc</c>.</impo>
226 swift 1.5 <note>If you aren't using Portage you do not need to specify DISTCC_DIR (i.e., just type distccmon-text N).</note>
227 blubber 1.2 </body>
228     </section>
229 swift 1.1 </chapter>
231     <chapter>
232 blubber 1.2 <title>Future Plans for Distcc and Gentoo</title>
233     <section>
234     <title>distcc-subnetscan</title>
235     <body>
236     <p><c>distcc-subnetscan</c> is a perl program in development that will scan a subnet for hosts that have a participating distcc daemon. Even this will be enhanced to test if the daemon on a remote host will conform to a specific <c>CHOST</c> setting to make cross-compiling easier.</p>
237     <p>The perl script is being kept at <uri link="http://dev.gentoo.org/~lisa/distcc/distcc-subnetscan/distcc-subnetscan.pl">right here</uri> until a more formal home can be found.</p>
238     </body>
239     </section>
240     <section>
241     <title>distcc-config</title>
242     <body>
243     <p><c>distcc-config</c>, the userland configuration tool for distcc is out of date. Soon it will be rewritten to be brought up the current version of distcc.</p>
244     </body>
245     </section>
246 swift 1.1 </chapter>
248     </guide>

  ViewVC Help
Powered by ViewVC 1.1.20