You are not logged in.
Pages: 1
Hi all I've got some problem using distcc.
I'm trying to setup a cross compiler on my arch x86_64 to speed up the compile time on my raspberry pi running on ArmArchlinux.
So I followed several guides and distcc seems to work but doesn't want to use the correct compiler.
My arm compiler toolchain is located in "/home/cyril/x-tools/arm-unknown-linux-gnueabi/bin". I've add line "PATH=/home/cyril/x-tools/arm-unknown-linux-gnueabi/bin:$PATH" in /etc/rc.d/distccd so distcc would use the gcc arm compiler instead of the x86_64 one.
When I compile a simple helloworld on my raspberry, the compilation is peformed on my x86_64 machine as excepted but the linkage fails because "hello.o: file not recognized: File format not recognized"
After comparing diffrent hello.o generated with the arm et x86_64 version of gcc, it seems that distcc still use the gcc located in /usr/bin instead of the one located in /home/cyril/x-tools/arm-unknown-linux-gnueabi/bin.
Any idea how to fix it ?
Thanks
Offline
Have you found a solution? I think I got the same problem here...
Offline
Don't forget that distcc itself is not involved in linking. Instead of tinkering with /etc/rc.d/distccd I'd recommend looking for a proper cross compilation framework (crosstools-ng maybe?).
For a workaround, though, try to mess around with the LD environment variable and set it to the appropriate linker.
Offline
Pages: 1