Changes between Version 3 and Version 4 of DevelopmentTools/DistCC


Ignore:
Timestamp:
May 21, 2011, 3:13:05 PM (8 years ago)
Author:
brecht
Comment:

you shouldn't run distccd on the Haiku machine

Legend:

Unmodified
Added
Removed
Modified
  • DevelopmentTools/DistCC

    v3 v4  
    3030../configure --use-32bit --alternative-gcc-output-dir ../generated.x86gcc4 --build-cross-tools ../../buildtools/
    3131cd ../generated.x86gcc4
    32 ../configure --alternative-gcc-output-dir ../generated.x86gcc2 --build-cross-tools-gcc4 x86 ../../buildtools/
     32../configure --use-32bit --alternative-gcc-output-dir ../generated.x86gcc2 --build-cross-tools-gcc4 x86 ../../buildtools/
    3333cd ..
    3434}}}
     
    6767
    6868* Add hostname or IP addresses of the helpers to {{{/boot/common/etc/distcc/hosts}}}
    69 
    70 * Uncomment {{{127.0.0.1}}} in {{{/boot/common/etc/distcc/hosts/clients.allow}}}
    71 
    72 * Start the distcc daemon
    73 {{{
    74 distccd --allow 127.0.0.1
    75 }}}
     69 Optionally add {{{localhost}}}. If this machine is slower than the helpers, it might slow down the build. You can easily find out by means of a quick benchmark. Even if you don't add {{{localhost}}}, it will still be busy distributing running jam, distributing jobs and linking.
    7670
    7771Now you can run {{{jam}}} as usual, but you should pass twice the total number of cores in the distcc network to the {{{-j}}} option. During a build, you can see what is happening by running