When I build xscreensaver on my system, it doesn't use distcc -- it also doesn't respect -jN values (always compiles only one file at a time). This is strange because looking in the ebuild, I see the usual "emake || die". emerge info: Portage 2.0.50-r10 (default-x86-2004.2, gcc-3.3.4, glibc-2.3.3.20040420-r1, 2.6.8.1) ================================================================= System uname: 2.6.8.1 i686 Celeron (Coppermine) Gentoo Base System version 1.5.3 distcc 2.16 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled] Autoconf: sys-devel/autoconf-2.59-r4 Automake: sys-devel/automake-1.8.5-r1 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-O3 -march=i686 -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" COMPILER="" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref /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="-O3 -march=i686 -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache distcc sandbox" GENTOO_MIRRORS="http://gentoo.osuosl.org http://distro.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j7" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X Xaw3d acpi alsa apm arts berkdb cjk crypt cups dga dvd emacs encode esd f77 faad fbcon fftw flac gcj gdbm gif gimpprint ginac gnome gpm gstreamer gtk gtk2 imlib jack jpeg leim libg++ libwww lirc live mad matroska mikmod mmx mng motif mozilla mpeg ncurses nls objc offensive oggvorbis opengl oss pam pdflib perl plotutils png ppds python qhull qt quicktime radeon readline scanner sdk sdl slang speex spell sse ssl svg tcpd tetex theora tiff truetype usb v4l video_cards_mach64 wxwindows x86 xinerama xml xml2 xmms xosd xv xvid zlib"
mh. lisa can you reproduce it? AFAIK it did always make use of distcc and spread compile processes over all nodes around.
Now that I have a little more experience with distcc, I'm reexamining this bug. xscreensaver *does* work with distcc however it never uses more than one CPU. But many other ebuilds also suffer from this problem: I think its just poor Makefiles that don't parallelize easily (i.e., the follow a linear ordering and there are no large collects of .o objects to farm out to distcc). I'm closing this bug because this isn't anything to do with distcc and its not particular to xscreensaver.