victor romanchuk writes: > >> i had noticed that distcc is peevish about CFLAGS: these should be > >> compatible on both client and server. in my case i made these > >> similar on both machines (laptop is core2duo and desktop is > >> core2quad; both are running amd64 arch) > > > > 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. Wonko