DistCC
Fri, 2006-03-24 01:12
Hey all, I have just installed DistCC on my laptop, and have set it all up in accordance with the manual. It works, and i can tell it works. The only problem is that it does not want to compile cross platform.
The error is as follows
distccd[11991] (dcc_execvp) ERROR: failed to exec powerpc-unknown-linux-gnu-gcc: Permission denied distcc[323] ERROR: compile findme.c on 192.168.2.7 failed with exit code 110 make[3]: *** [findme.o] Error 1 make[3]: *** Waiting for unfinished jobs.... distccd[11992] (dcc_execvp) ERROR: failed to exec powerpc-unknown-linux-gnu-gcc: Permission denied distcc[326] ERROR: compile popt.c on 192.168.2.7 failed with exit code 110 make[3]: *** [popt.o] Error 1 make[3]: Leaving directory `/var/tmp/portage/irssi-0.8.10/work/irssi-0.8.10/src/ lib-popt' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/var/tmp/portage/irssi-0.8.10/work/irssi-0.8.10/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/irssi-0.8.10/work/irssi-0.8.10' make: *** [all] Error 2 !!! ERROR: net-irc/irssi-0.8.10 failed. !!! Function src_compile, Line 58, Exitcode 2 !!! emake failed !!! If you need support, post the topmost build error, NOT this status message.
From where i am standing, basically it is erroring on the other computer, as it cant find the make option "powerpc-unknown-linux-gnu-gcc"
This makes sense to me, but im pretty sure it is possible cross plat form.
The other computer is an AMD athlon with FC4, the laptop is a G4 with genoo.
Any other help would be great!
My usderstanding of distCC was that it was used to shorten compile times for machines of similar spec, that is if you have a AMD XP2000+ and an P4 or somthing you compile on one, and then you use distCC to make the compile on the second PC much faster.
You have a x86 proc on one machine and a ppc on the other - so I don't see how it would work.
dylunio
distcc is a program to distribute builds of C, C++, Objective C or Objective C++ code across several machines on a network. distcc should always generate the same results as a local build, is simple to install and use, and is usually much faster than a local compile.
distcc does not require all machines to share a filesystem, have synchronized clocks, or to have the same libraries or header files installed. They can even have different processors or operating systems, if cross-compilers are installed.
Still nothing
From here:
As long as the networked boxes are all using the same toolchain built for the same processor architecture, no special distcc setup is required.
It seems it is possible somehow, so see if that page is any help.