|
Lines 48-54
Link Here
|
| 48 |
|
48 |
|
| 49 |
<p> |
49 |
<p> |
| 50 |
Distcc is a program designed to distribute compiling tasks across a network to |
50 |
Distcc is a program designed to distribute compiling tasks across a network to |
| 51 |
participating hosts. It is comprised of a server, <c>distccd</c> and a client |
51 |
participating hosts. It is comprised of a server, <c>distccd</c>, and a client |
| 52 |
program, <c>distcc</c>. Distcc can work transparently with <uri link="http://ccache.samba.org">ccache</uri> and Portage with a little work. |
52 |
program, <c>distcc</c>. Distcc can work transparently with <uri link="http://ccache.samba.org">ccache</uri> and Portage with a little work. |
| 53 |
</p> |
53 |
</p> |
| 54 |
|
54 |
|
|
Lines 60-67
Link Here
|
| 60 |
|
60 |
|
| 61 |
<p> |
61 |
<p> |
| 62 |
If you are planning on using distcc to help you bootstrap a Gentoo installation, |
62 |
If you are planning on using distcc to help you bootstrap a Gentoo installation, |
| 63 |
make sure you read the part on <uri link="#bootstrapping">Using distcc to |
63 |
make sure you read the section <uri link="#bootstrapping">Using distcc to |
| 64 |
Bootstrap</uri> which is situated further down in this document. |
64 |
Bootstrap</uri>, which is situated further down in this document. |
| 65 |
</p> |
65 |
</p> |
| 66 |
|
66 |
|
| 67 |
</body> |
67 |
</body> |
|
Lines 75-83
Link Here
|
| 75 |
<body> |
75 |
<body> |
| 76 |
|
76 |
|
| 77 |
<p> |
77 |
<p> |
| 78 |
To start off with, to use Distcc all of the computers on your network need to |
78 |
In order to use Distcc, all of the computers on your network need to |
| 79 |
have the same GCC versions. Mixing 3.3.x (where the x varies) is okay, but |
79 |
have the same GCC versions. Mixing 3.3.x (where the x varies) is okay, but |
| 80 |
mixing 3.3.x and 3.2.x is not: your programs <b>will</b> have errors in it. |
80 |
mixing 3.3.x and 3.2.x <b>will</b> result in your programs having errors in them. |
| 81 |
</p> |
81 |
</p> |
| 82 |
|
82 |
|
| 83 |
</body> |
83 |
</body> |
|
Lines 87-93
Link Here
|
| 87 |
<body> |
87 |
<body> |
| 88 |
|
88 |
|
| 89 |
<p> |
89 |
<p> |
| 90 |
There are a couple of options you should know about before you start |
90 |
There are a couple of options you should be aware of before you start |
| 91 |
installing distcc. |
91 |
installing distcc. |
| 92 |
</p> |
92 |
</p> |
| 93 |
|
93 |
|
|
Lines 109-115
Link Here
|
| 109 |
<body> |
109 |
<body> |
| 110 |
|
110 |
|
| 111 |
<p> |
111 |
<p> |
| 112 |
Setting up distcc is easy to do with Portage. Execute the following steps on |
112 |
Setting up Portage to use distcc is easy. Execute the following steps on |
| 113 |
each system that should participate in the distributed compiling: |
113 |
each system that should participate in the distributed compiling: |
| 114 |
</p> |
114 |
</p> |
| 115 |
|
115 |
|
|
Lines 123-131
Link Here
|
| 123 |
FEATURES="distcc" |
123 |
FEATURES="distcc" |
| 124 |
</pre> |
124 |
</pre> |
| 125 |
|
125 |
|
|
|
126 |
</body> |
| 127 |
</section> |
| 128 |
<section> |
| 129 |
<title>Specifying Participating Hosts</title> |
| 130 |
<body> |
| 131 |
|
| 126 |
<p> |
132 |
<p> |
| 127 |
Next you have to specify what hosts you want to use. Use the |
133 |
Use the <c>distcc-config</c> command to set the list of hosts. Here is an example of |
| 128 |
<c>distcc-config</c> command to set the list of hosts. Here is an example of |
|
|
| 129 |
some hosts that might be in your list: |
134 |
some hosts that might be in your list: |
| 130 |
</p> |
135 |
</p> |
| 131 |
|
136 |
|
|
Lines 166-176
Link Here
|
| 166 |
|
171 |
|
| 167 |
<p> |
172 |
<p> |
| 168 |
Edit <path>/etc/conf.d/distccd</path> to your needs and be sure to set the |
173 |
Edit <path>/etc/conf.d/distccd</path> to your needs and be sure to set the |
| 169 |
<c>--allow</c> directive to allow only hosts you trust. For more information |
174 |
<c>--allow</c> directive to allow only hosts you trust. For added security, you should also use the <c>--listen</c> |
| 170 |
please see the <uri link="http://distcc.samba.org/security.html">Distcc Security |
175 |
directive to tell the distcc daemon what IP to listen on (for multi-homed |
| 171 |
Design</uri>. For added security you should also use the <c>--listen</c> |
176 |
systems). More information on distcc security can be found at <uri link="http://distcc.samba.org/security.html">Distcc Security |
| 172 |
directive to tell the Distcc daemon what IP to listen on (for multi-homed |
177 |
Design</uri>. |
| 173 |
systems). |
|
|
| 174 |
</p> |
178 |
</p> |
| 175 |
|
179 |
|
| 176 |
<p> |
180 |
<p> |
|
Lines 191-197
Link Here
|
| 191 |
<body> |
195 |
<body> |
| 192 |
|
196 |
|
| 193 |
<p> |
197 |
<p> |
| 194 |
This is in some cases easier than the Portage setup. What you have to do is |
198 |
This is, in some cases, easier than the Portage setup. What you have to do is |
| 195 |
update your <c>PATH</c> variable to include <path>/usr/lib/distcc/bin</path> |
199 |
update your <c>PATH</c> variable to include <path>/usr/lib/distcc/bin</path> |
| 196 |
in front of the directory that contains <c>gcc</c> (<path>/usr/bin</path>). |
200 |
in front of the directory that contains <c>gcc</c> (<path>/usr/bin</path>). |
| 197 |
However, there is a caveat. If you use ccache you have to put distcc after |
201 |
However, there is a caveat. If you use ccache you have to put distcc after |
|
Lines 230-241
Link Here
|
| 230 |
</body> |
234 |
</body> |
| 231 |
</section> |
235 |
</section> |
| 232 |
<section> |
236 |
<section> |
| 233 |
<title>An Introduction to Cross-compiling</title> |
237 |
<title>An Introduction to Cross-Compiling</title> |
| 234 |
<body> |
238 |
<body> |
| 235 |
|
239 |
|
| 236 |
<p> |
240 |
<p> |
| 237 |
If you want to give Cross-compiling a try you can to follow <uri link="http://dev.gentoo.org/~vapier/CROSS-COMPILE-HOWTO">The Cross Compile |
241 |
If you want to give cross-compiling a try, you can read <uri link="http://dev.gentoo.org/~vapier/CROSS-COMPILE-HOWTO">The Cross Compile |
| 238 |
HOWTO</uri>; Crossdev is depreciated. |
242 |
HOWTO</uri>; Crossdev is deprecated. |
| 239 |
</p> |
243 |
</p> |
| 240 |
|
244 |
|
| 241 |
</body> |
245 |
</body> |
|
Lines 311-324
Link Here
|
| 311 |
</pre> |
315 |
</pre> |
| 312 |
|
316 |
|
| 313 |
<p> |
317 |
<p> |
| 314 |
distcc is now set up to bootstrap! Continue the official installation |
318 |
Distcc is now set up to bootstrap! Continue with the official installation |
| 315 |
instructions and <e>do not forget</e> to re-emerge distcc after <c>emerge |
319 |
instructions and <e>do not forget</e> to re-emerge distcc after <c>emerge |
| 316 |
system</c>. This is to make sure that all of the dependencies you want are |
320 |
system</c>. This is to make sure that all of the dependencies you want are |
| 317 |
installed as well. |
321 |
installed as well. |
| 318 |
</p> |
322 |
</p> |
| 319 |
|
323 |
|
| 320 |
<note> |
324 |
<note> |
| 321 |
During bootstrap and <c>emerge system</c> Distcc may not appear to be used. |
325 |
During bootstrap and <c>emerge system</c> distcc may not appear to be used. |
| 322 |
This is expected as some ebuilds do not work well with distcc, so they |
326 |
This is expected as some ebuilds do not work well with distcc, so they |
| 323 |
intentionally disable it. |
327 |
intentionally disable it. |
| 324 |
</note> |
328 |
</note> |