On 08/09/12 17:03, "Roland Häder" wrote:
I was reading this: http://www.gentoo.org/doc/en/cross-compiling-distcc.xmlI also read it far before I wrote my email.It specifically mentions you need crossdev: If you are cross-compiling between different subarchitectures for Intel x86 (e.g. i586 and i686), you must still build a full cross-toolchain for the desired CHOST, or else the compilation will fail. I suppose any cross compiler might be enough and you don't need crossdev. I don't know.I need to repeat: The other nodes are all running Debian and there is *no* crossdev package. And I wrote in my initial mail, that I was already able to cross-compile other Gentoo packages on these nodes as the parameters -m32 and -march=i686 were *provided* by those packages which seems to be *not* the case with e.g. klibc All I want is that the klibc package is honoring the global CFLAGS or else I have to temporary disable distcc (FEATURES variable needs to be commented out) for klibc, emerge klibc and then re-enable distcc to have a great speedup for other packages (that are honoring CFLAGS from make.conf). I do that now what I wrote but it is really annoying to cannot leave the compilation unattended. I repeat once more: cross-compiling is possible on my nodes, so there is absolutely no need to setup such "cross-toolchains" because it works.
I'd say it worked for you by accident (because of multilib). But I doubt this is supposed to actually work that way.
