When compiling named packade with distcc enabled, several access violations are reported resulting in a failed emerge. The bug is reproducable on my system, but I have not had the oppertunity to attempt to reproduce on my other system. >>> Completed installing into /var/tmp/portage/gdk-pixbuf-0.22.0/image/ --------------------------- ACCESS VIOLATION SUMMARY --------------------------- LOG FILE = "/tmp/sandbox-gdk-pixbuf-0.22.0-8999.log" open_wr: /.distcc/lock/cpu_localhost_0 open_wr: /.distcc/lock/cpu_localhost_0 open_wr: /.distcc/lock/cpu_localhost_0 open_wr: /.distcc/lock/cpu_localhost_0 open_wr: /.distcc/lock/cpu_localhost_0 open_wr: /.distcc/lock/cpu_localhost_0 open_wr: /.distcc/lock/cpu_localhost_0 open_wr: /.distcc/lock/cpu_localhost_0 open_wr: /.distcc/lock/cpu_localhost_0 open_wr: /.distcc/lock/cpu_localhost_0 open_wr: /.distcc/lock/cpu_localhost_0 -------------------------------------------------------------------------------- emerge info Portage 2.0.49-r15 (default-x86-1.4, gcc-3.2.3, glibc-2.3.2-r1, 2.4.22-2.4.22) ================================================================= System uname: 2.4.22-2.4.22 i686 AMD Athlon(tm) XP 2400+ Gentoo Base System version 1.4.3.10 distcc 2.11.1 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled] ccache version 2.3 [enabled] ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-march=athlon -O3 -pipe -funroll-loops" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /var/qmail/control /usr/kde/2/share/config /usr/kde/3/share/config /usr/X11R6/lib/X11/xkb /usr/kde/3.1/share/config /usr/share/config" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-march=athlon -O3 -pipe -funroll-loops" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs sandbox userpriv usersandbox ccache distcc" GENTOO_MIRRORS="ftp://ftp.uninett.no/pub/linux/Gentoo ftp://gentoo.linux.no/pub/gentoo/ ftp://trumpetti.atm.tut.fi/gentoo/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="x86 oss apm avi crypt encode gif jpeg libg++ libwww mad mikmod mpeg ncurses nls pdflib png quicktime spell truetype xml2 xmms xv zlib gdbm berkdb slang readline svga tcltk java sdl gpm tcpd pam ssl perl python esd imlib oggvorbis gtk qt opengl cdr X dga Xaw3d -arts -cups -foomaticdb -bonobo -guile -gnome -kde -gtk2 -motif"
this is a distcc "bug." Is PORTAGE_TMPDIR commented or not defined in your /etc/make.conf?
It was commented away. Re-emerging with PORTAGE_TMPDIR set to /var/tmp/ gave exactly the same results. After some closer inspection, this bug should perhaps be marked as a dup of 33162 if this is a general distcc problem.
I don't think its a dupe of bug 33162. He's having permission issues, not sandbox ones. Do you have a DISTCC_DIR in /etc/make.conf at all? If so, remove it and try to compile again.
OK, took a second look. Found this line in my make.conf: DISTCC_DIR="${PORT_TMPDIR}/.distcc" The problem is that PORT_TMPDIR isn't anything. It should perhaps be PORTAGE_TMPDIR. Higher up in the file I have the line: PORTAGE_TMPDIR=/var/tmp Changing the DISTCC_DIR to depend on the defined variable seems to solve the problem. Having taken a look at the defult make.conf I can confirm that this incompatibility between the variable names does in fact exist.
Seems fixed? Try updating Portage and Distcc if this persists. Make sure DISTCC_DIR is not defined anywhere in /etc/make.conf. Repoen if this persists.
Everything seems to work perfectly. Both with the DISTCC_DIR undefined and with it defined to its defalut value. One down...
*** Bug 142133 has been marked as a duplicate of this bug. ***
