On 08/22/2011 01:41 PM, Alex Schuster wrote: >>> > > I don't think this is true - as long as the CHOST is identical, there >>> > > should be no problem. >> > >> > CHOST defines the arch (i686, amd64, arm ..) whilst CFLAGS control gcc >> > behavior and the binary code generation produced by compiler. in my case >> > core2quad (q8300) i'm using in the desktop supports sse4.1 instruction >> > set and notebook powered with core2duo (t7600) does not have that cpu >> > feature. having option `-msse4.1' set in CFLAGS at desktop side will >> > causes frequent compilation failures (initiated by distcc) or, in worst >> > case - arbitrary crashes at notebook when running binaries compiled in >> > distributed distcc environment > But how could the gcc on the desktop, called via distcc, even see the CFLAGS > in the desktops make.conf? This just cannot be. > I have been using march=athlon-xp on my desktop, and yet used it as distcc > server for my Pentium-III notebook for years. Worked fine.
The arguments sent to gcc tell it what kind of object gcc is supposed to create. If gcc cannot create the object you request because it's not the right "kind" of gcc, implies that, within the same gcc version, it is unable to reproduce object files.
