When I compile glibc/python using distcc enabled portage the compile fails. Reproducible: Always Steps to Reproduce: 1. Setup distcc to work with portage 2. emerge glibc or pythong (or: -u system in my case) Actual Results: The compile fails with an error about unreconized format. Below is the error output from an attempted python emerge: Parser/bitset.o: file not recognized: File format not recognized collect2: ld returned 1 exit status make: *** [Parser/pgen] Error 1 make: *** Waiting for unfinished jobs.... !!! ERROR: dev-lang/python-2.2.3-r1 failed. !!! Function src_compile, Line 73, Exitcode 2 !!! Parallel make failed Expected Results: glibc/python to compile correctly then be merged. I'm just reporting this in case there is a way to say "this package doesn't play well with distcc." (I disabled distcc while I installed that latest glibc) Portage 2.0.48-r1 (default-x86-1.4, gcc-3.2.3, glibc-2.3.2-r1) ================================================================= System uname: 2.4.20-xfs_pre6 i686 Intel(R) Pentium(R) 4 CPU 1.80GHz GENTOO_MIRRORS="http://csociety-ftp.ecn.purdue.edu/pub/gentoo/ ftp://ftp.gtlib.cc.gatech.edu/pub/gentoo" CONFIG_PROTECT="/etc /var/qmail/control /usr/kde/2/share/config /usr/kde/3/share/config /var/bind /usr/X11R6/lib/X11/xkb /opt/tomcat/conf /usr/kde/3.1/share/config /usr/share/config" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" PORTDIR="/usr/portage" DISTDIR="/usr/portage/distfiles" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR_OVERLAY="/usr/local/portage" USE="x86 oss apm avi crypt encode foomaticdb gif jpeg gnome libg++ libwww mad mikmod mmx mpeg ncurses nls pdflib png spell truetype xml2 xmms xv zlib gdbm berkdb slang readline arts svga java postgres X sdl gpm tcpd pam ssl perl python imlib oggvorbis gtk qt kde motif opengl -esd -3dnow ipv6 tcltk tiff cups mozilla alsa -ldap quicktime" COMPILER="gcc3" CHOST="i686-pc-linux-gnu" CFLAGS="-march=pentium4 -O3 -pipe" CXXFLAGS="-march=pentium4 -O3 -pipe" ACCEPT_KEYWORDS="x86" MAKEOPTS="-j8" AUTOCLEAN="yes" SYNC="rsync://rsync2.us.gentoo.org/gentoo-portage" FEATURES="sandbox ccache distcc"
hmm works on my distcc. what version of distcc are you using on both the server and the client? i dunno, but have you tried using less optimisations? there have been known problems with glibc and python using -march=pentium4 (try searching bugzilla for "pentium4 python"
It also worked on distcc-2.8-r2 here.
Sorry i didn't track this down more. I've narrowed the problem down to one of the nodes in our distcc cluster. I've marked this bugs as INVALID.