Firstly, I try the distcc possibilities with a little program (peacock), with : make -j3 CC="distcc". I use two AMD-XP, and it works fine. Then, I tried to link distcc with emerge (FEATURES="distcc" CC="distcc" -or "distcc gcc"- and CXX="distcc g++", MAKEOPTS="-j3"). I tried with : emerge xfce4-toys and it didn't work. So I did the same test with another package (pilot-link), and logged it (http://www.enseirb.fr/~varaldi/emergeLog/ for the logs and some config files). It didn't work too. I don't see the problem, and asked for some help on #gentoofr@freenode, and nobody could find the problem. no problem with iptables, nor with the two PCs. both PCs have been upgraded this morning (emerge rsync && emerge -UD world ok for both of them) Reproducible: Always Steps to Reproduce: 1. emerge APackageThatUsegccToCompile 2. that's all folks 3. (see the activity of distcc with distccmon-text 1 and tcpdump and top -d1) Actual Results: The package is well installed, but the compilation seemed not to use distcc Expected Results: use the distcc possibilities ^@^. However, in emerge info, COMPILER is set to gcc3, I don't know if it's a problem or not. CC is set to "distcc gcc" and CXX to "distcc g++" as I read here : http://forums.gentoo.org/viewtopic.php?t=16455 Portage 2.0.49-r21 (default-x86-1.4, gcc-3.2.3, glibc-2.3.2-r3, 2.4.20-gentoo-r7 ) ================================================================= System uname: 2.4.20-gentoo-r7 i686 AMD Athlon(tm) XP 1600+ Gentoo Base System version 1.4.3.10p1 distcc 2.11.1 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled ] ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O2 -mcpu=i686 -pipe" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.1 /share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-O2 -mcpu=i686 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache distcc sandbox" GENTOO_MIRRORS="ftp://ftp.snt.utwente.nl/pub/os/linux/gentoo" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/var/tmp/distccd" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X aalib apm arts avi berkdb bonobo cdr crypt encode esd foomaticdb gdbm gif gnome gpm gtk gtk2 gtkhtml imlib java jpeg kde libg++ libwww mad mikmod motif m peg mysql ncurses nls oggvorbis opengl oss pam pdflib perl png python qt quickti me readline sdl slang spell ssl svga tcltk tcpd truetype x86 xml2 xmms xv zlib"
*** Bug 38644 has been marked as a duplicate of this bug. ***
Have you followed the directions for enabling it for portage at http://www.gentoo.org/doc/en/distcc.xml ? - Steve
Yes, I did.
CC="distcc gcc" CXX="distcc g++" DISTCC_HOSTS="192.168.0.1" Remove those definitions from your /etc/make.conf file and try again. Those lines are not found in the howto guide and should not have been added or modified. By the way, log files would be best named foo.log.txt - this will force browsers to open the file without a prompt to save as.
I still have the problem without CC=, CXX= and DISTCC_HOSTS= in the /etc/make.conf file.
this is a distcc bug, clearly. What host is 192.168.0.1? Is that the machine of the box that `emerge` is issued on? Follow the distcc guide to install and then create another log please.
I have : 192.168.0.3 : it makes the "emerge package" 192.168.0.1 : it would make compilation for .0.3 For the last point, I'll make it next night, cause I don't have enough time this day ...
Today, I got a funny thing : I wanted to emerge STDport on 192.168.0.1, which was as well configured to use distcc. Then I noticed 192.168.0.3 was a bit slow, so I did a top -d1, and it appeared that some cc1plus had been launched via the distcc's user ID. By the way, the compilation run slow, so I stopped it. As a log, here is one compilation line on 192.168.0.1 : c++ -pthread -fexceptions -I../stlport -W -Wno-sign-compare -Wno-unused -Wno-uninitialized -D_STLP_USE_GLIBC -O3 -march=athlon-xp -funroll-loops -pipe -fPIC stdio_streambuf.cpp -c -o ../lib/obj/GCC-LINUX/ReleaseD/stdio_streambuf.o We can see that nothing is very special on it. and distccmon-text 1 on both computers gave me the same result : nothing. It looks amazing, but some processus may have been launched by 0.1, via distcc, but without using it ... None of my two configurations have changed, and they still have the same as with the bug report (except the modifications told in the comments). Any idea ? ps : with a tcpdump on the 3632 port on 0.3, no activity ... and the compilation stops at one line, but I don't see why.
I make it fixed. The problem was that iptables was blocking some requests on one of the computers. Shame on me :((( (then I'm gonna open the windows, and ...)
