Trying to emerge procps fails for me when using distcc: [...] gcc -c -D_GNU_SOURCE -I proc -fno-common -ffast-math -W -Wall -Wshadow -Wcast-align -Wredundant-decls -Wbad-function-cast -Wcast-qual -Wwrite-strings -Waggregate-return -Wstrict-prototypes -Wmissing-prototypes -O2 -march=i686 -fomit-frame-pointer -Wdeclaration-after-statement -Wpadded -Wstrict-aliasing -frename-registers -fomit-frame-pointer -fno-inline-functions -DSHARED=1 -fpic proc/escape.c -o proc/escape.o cc1: error: unrecognized option `-Wdeclaration-after-statement' distcc[12832] ERROR: compile proc/devname.c on 192.168.0.3/10 failed cc1: error: unrecognized option `-Wdeclaration-after-statement' distcc[12829] ERROR: compile proc/alloc.c on 192.168.0.3/10 failed make: *** [proc/devname.o] Fehler 1 make: *** Warte auf noch nicht beendete Prozesse... make: *** [proc/alloc.o] Fehler 1 !!! ERROR: sys-apps/procps-3.2.4-r2 failed. !!! Function src_compile, Line 51, Exitcode 2 !!! make failed !!! If you need support, post the topmost build error, NOT this status message. Localhost uses gcc-Version 3.3.4 20040623 (Gentoo Linux 3.3.4-r1, ssp-3.3.2-2, pie-8.7.6) 192.168.0.3 uses gcc-Version 3.3.5 (Gentoo Linux 3.3.5-r1, ssp-3.3.2-3, pie-8.7.7.1) These are the only two hosts running distcc: bash-2.05b# distcc-config --get-hosts 127.0.0.1/1 192.168.0.3/10 Without FEATURES="distcc" it compiles. Reproducible: Always Steps to Reproduce: 1. Use portage with FEATURES="distcc" with the distcc configuration described above 2. emerge procps bash-2.05b# emerge info Portage 2.0.51-r15 (default-linux/x86/2004.3, gcc-3.3.4, glibc-2.3.4.20040808-r1, 2.6.8-gentoo i686) ================================================================= System uname: 2.6.8-gentoo i686 Mobile Intel(R) Celeron(R) CPU 2.50GHz Gentoo Base System version 1.4.16 Python: dev-lang/python-2.3.4 [2.3.4 (#1, Dec 18 2004, 21:23:19)] distcc 2.16 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled] dev-lang/python: 2.3.4 sys-devel/autoconf: 2.59-r5 sys-devel/automake: 1.8.5-r1 sys-devel/binutils: 2.15.90.0.1.1-r3 sys-devel/libtool: 1.4.3-r4, 1.5.2-r7 virtual/os-headers: 2.4.21-r1 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O2 -march=i686 -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -march=i686 -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distcc distlocks sandbox sfperms" GENTOO_MIRRORS="ftp://sunsite.informatik.rwth-aachen.de/pub/Linux/gentoo ftp:///ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 X alsa apm arts avi berkdb bitmap-fonts cdr crypt cups dts dvd dvdr dvdread encode esd f77 fam flac font-server foomaticdb fortran gdbm gif gphoto2 gpm gtk gtk2 guile imagemagick imlib ipv6 java jpeg kde libg++ libwww mad mikmod motif mpeg mysql ncurses nls oggvorbis opengl oss pam pdflib perl png python quicktime readline sdl spell ssl svga tcpd tetex tiff truetype truetype-fonts type1-fonts xml2 xmms xv zlib" Unset: ASFLAGS, CBUILD, CTARGET, LDFLAGS, PORTDIR_OVERLAY
Use _always_ exactly the same compiler version on all machines. gcc-3.3 and 3.4 do no even have the same C++ ABI.
In this case, please correct the gentoo distcc HOWTO: http://www.gentoo.org/doc/en/distcc.xml It says: "Mixing 3.3.x (where the x varies) is okay, but mixing 3.3.x and 3.2.x will result in your programs having errors in them." Obviously, mixing 3.3.x is NOT okay.
Sorry, somehow I read you mixed gcc 3.4 and 3.3. In general you can use a configuration with different gcc bugfix releases. I would always use the same versions, though.
dems da ropes ! 3.3.4 supports -Wdeclaration-after-statement but 3.3.5 doesnt in general, minor gcc's should be compat, but not always (as you can see here)
