Currently, portage starts distcc-pump server in src_compile(), and terminates when leaving that phase. As a result, compilations done e.g. in src_test() result in a lot of errors alike: distcc[22139] ERROR: failed to connect to UNIX-DOMAIN /tmp/distcc-pump.6716Nx/socket: No such file or directory distcc[22139] (dcc_build_somewhere) Warning: failed to get includes from include server, preprocessing locally (and obviously lack of pump use)
(In reply to Michał Górny from comment #0) > compilations done e.g. in src_test() result in a lot of errors alike: What kind of compilations are these? Compilation of tests are usually placed in src_compile; or are these tests that do compilations, like in a compiler?
Send previous message too fast; I think that in the latter case, tests that do compilations, you might not want them to run through distcc as you will want to test the compilation on the local host and not have it fail due to distcc woes.
Regular C programs that are built during src_test(). This is done e.g. with proper autotools packages that use stuff like 'check_PROGRAMS' instead of building tests all the time or on random conditionals.
Now in git.
