On Monday, May 04, 2015 3:41:54 PM Walter Dnes wrote: > Why is seamonkey the only program (so far for me) that needs "-m32"? > Would it need "-m64" if it was being cross-compiled on a 32-bit host > system for 64-bit client? Is there a wiki that we can contribute this > info to?
It has to do with my last post. Basicly the makefiles are invoking the full compiler name for the files that are meant to run on the target but it invokes just gcc for the files that are meant to run on the host. This is in the context of cross-compiling, not distcc, so the file that's failing is meant to run locally (it's a custom build tool). If you where compiling locally (or in two machines with the same compiler) it would not matter cause the host and target compiler are the same, but when distcc comes in it builds those files with the host (system) compiler on the host. Changing the c++, cc, gcc, and g++ symlinks to a wrapper script that invokes the compiler by it's full name as show in the RaspberryPi wiki page *should* fix it. -- Fernando Rodriguez
