Different processors use different sets of commands, and hence the "binaries" produced by compilers for different platforms are different. distcc calls gcc the same way it would be called by the local machine; since you wouldn't expect to be able to compile on your Linux PC for your Mac (even if you run `./configure` on the source on the Mac & copy the Makefile across), you shouldn't expect the results produced by distcc to work that easily, either.
It's my understanding that to produce a cross-compilation�"toolchain" you need to do stuff like recompile a separate set of the c-libraries (I think glibc & perhaps others) using suitable flags to gcc to tell it which architecture the libraries are intended to produce binaries for; I think you then need to compile a separate instance of gcc, again using suitable flags when compiling to tell it which architecture for which the resultant compiler should produce suitable binaries for.
When I started researching this I wasn't easily able to find anyone with the time & experience to teach me. I'd like to learn more about it, but will probably end up waiting for Portage-NG which (I think) should handle this seamlessly.
Stroller.
On Jan 11, 2004, at 6:36 pm, Lotas T Smartman wrote:
so, since gcc is version 3.3.2 20031218 (Gentoo Linux 3.3.2-r5, propolice-3.3-7) on my workstation and 3.3 20030304 (apple computer, inc. build 1495) on the mac, it should in theory work, yea? ...
Quite so. As it says at their home page http://distcc.samba.org/ "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."
-- [EMAIL PROTECTED] mailing list
