This is in reference to closed bug 51532. I'm opening this bug for two reasons. 1) Commenting out the DISTCC_DIR line in /etc/make.conf is a _workaround_. This bug should not be considered resolved until the portage ebuild removes this line from make.conf _and_ after the distcc guide is updated. 2) This behaviour starts happening _after_ the emerge of 'coreutils-5.2.1'. i.e. There may be more going on here than is readily apparent. I run distcc on three machines. Each machine halted with distcc access violations on it's following respective ebuild _after_ emerging coreutils. In one case, this was 'openssl-0.9.7d-r1'. The second was 'mozilla-1.7'. And the third was 'python-2.3.4'. Turnnig off distcc allowed compilation to continue in each case. Reproducible: Always Steps to Reproduce:
paste the access violations please
Created attachment 33722 [details] distcc related png First of all, I must apologise. It did not occur to me to save the access violation logs - and it should have as I know better. I saw your comment about commenting out the DISTCC_DIR line and immediately proceeded to do so. The only thing I have is the attatched png. It is taken from machine 'flambe'. It shows the results of 'emerge -puUvD world' twice. The first time was when I was checking to see how many packages I had left after having done gcc-3.3.3. The second is after coreutils finished emerging and openssl borked with the access violation messages. This is the emerge info for 'flambe': flambe root # emerge info Portage 2.0.50-r8 (default-x86-1.4, gcc-3.3.3, glibc-2.3.3_pre20040420-r0, 2.4.24) ================================================================= System uname: 2.4.24 i586 Pentium 75 - 200 Gentoo Base System version 1.4.16 distcc 2.14 i586-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled] Autoconf: sys-devel/autoconf-2.59-r3 Automake: sys-devel/automake-1.8.5-r1 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-Os -march=pentium -fomit-frame-pointer -pipe" CHOST="i586-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-Os -march=pentium -fomit-frame-pointer -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache distcc sandbox" GENTOO_MIRRORS="http://gentoo.oregonstate.edu http://distro.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j5" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="apm berkdb crypt gdbm gpm gtk2 libg++ libwww mad mikmod ncurses nls oss pam perl python readline slang spell ssl svga tcpd x86 xml2 zlib" flambe root # As you can see, 'flambe' is a 120 classic pentium. It has 64 meg of ram. I use it as my firewall. Compiling gcc on this machine in standalone mode takes three days. With distcc running and working off my primary workstation, it takes less than 5 hours. This is the emerge info for my primary machine: dragonfyre root # emerge info Portage 2.0.50-r8 (default-x86-2004.0, gcc-3.3.3, glibc-2.3.3.20040420-r0, 2.6.7) ================================================================= System uname: 2.6.7 i686 AMD Athlon(tm) XP 2500+ Gentoo Base System version 1.4.16 distcc 2.14 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="-march=athlon-xp -O3 -fomit-frame-pointer -pipe" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.2/share/config /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=athlon-xp -O3 -fomit-frame-pointer -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache distcc sandbox" GENTOO_MIRRORS="http://gentoo.oregonstate.edu http://distro.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="3dnow X Xaw3d accessibility alsa apache2 apm arts audiofile avi berkdb bonobo cdr crypt cups curl dga directfb divx4linux doc dvd dvdr encode esd ethereal fbcon flac foomaticdb freetds gd gdbm gif gnome gpm gstreamer gtk gtk2 gtkhtml guile icq imagemagic imlib innodb jabber java jikes jpeg kde lcms ldap lesstiff libg++ libwww mad maildir mikmod motif mozilla mpeg mysql nas ncurses nls odbc offensive oggvorbis opengl oss pam pda pdflib perl png postgres ppds python qt quicktime readline ruby samba scanner sdl slang speex spell ssl svga tcltk tcpd theora truetype unicode usb winf wxwindows x86 xeo xinerama xml2 xmms xv yahoo zlib" dragonfyre root # Other than the difference in kernels, I keep gcc and glibc levels pretty tightly in sync. The third machine is in FL (I'm in NJ) and is the machine I set up for my mother. She has it turned off at the moment. :-( When I got the access violations on the other machines, I noticed that each machine had borked _after_ coreutils had finished compiling. The access violation messages are identical as the messages in bug 51532. The only difference was the package centric location of the access violation log. Sorry I can't be more helpful. I'm not prepared at this time to 'roll back' and reproduce it on my live machines. I will look into seeing if I can fire up a testing machine but I can't promise being able to get said machine. If I can provide any other information, please let me know.
DOH!! I was looking in the wrong places for the access violation logs. This is the one from 'dragonfyre': sandbox-net-www_-_mozilla-1.7-3730.log open_wr: /.distcc/lock/cpu_localhost_0 open_wr: /.distcc/state/binstate_3773 unlink: /.distcc/state/binstate_3773 This is the one from 'flambe' (I tried it four times with variations): -rw-rw-r-- 1 root portage 121 Jun 19 01:01 sandbox-dev-libs_-_openssl-0.9.7d-r1-7921.log -rw-rw-r-- 1 root portage 121 Jun 19 07:17 sandbox-dev-libs_-_openssl-0.9.7d-r1-8354.log -rw-rw-r-- 1 root portage 121 Jun 19 07:21 sandbox-dev-libs_-_openssl-0.9.7d-r1-8752.log -rw-rw-r-- 1 root portage 121 Jun 19 07:26 sandbox-dev-libs_-_openssl-0.9.7d-r1-9229.log flambe tmp # cat sandbox-dev-libs_-_openssl-0.9.7d-r1-7921.log open_wr: /.distcc/lock/cpu_localhost_0 open_wr: /.distcc/state/binstate_8028 unlink: /.distcc/state/binstate_8028 flambe tmp # Hope this helps!
One more detail. If memory serves me correctly - in each case, the access violation messages appeared immediately after all the patches were applied. I can't remember if I got the 'source unpacked' message. However I do know that the violation messages appeared before any of the 'checking' messages I expected to see from the 'make' command. ... I think. :-(
i'm having the same problem with openssl: >>> md5 src_uri ;-) openssl-0.9.7d.tar.gz >>> md5 src_uri ;-) openssl-0.9.6m.tar.gz >>> Unpacking source... >>> Unpacking openssl-0.9.7d.tar.gz to /var/tmp/portage/openssl-0.9.7d-r1/work >>> Unpacking openssl-0.9.6m.tar.gz to /var/tmp/portage/openssl-0.9.7d-r1/work * Applying openssl-0.9.7d-gentoo.diff... [ ok ] * Applying openssl-0.9.7d-smime.patch... [ ok ] ACCESS DENIED open_wr: /distcc/lock/cpu_localhost_0 ACCESS DENIED open_wr: /distcc/state/binstate_14168 ACCESS DENIED unlink: /distcc/state/binstate_14168 >>> Source unpacked. --------------------------- ACCESS VIOLATION SUMMARY --------------------------- LOG FILE = "/tmp/sandbox-dev-libs_-_openssl-0.9.7d-r1-14054.log" open_wr: /distcc/lock/cpu_localhost_0 open_wr: /distcc/state/binstate_14168 unlink: /distcc/state/binstate_14168 -------------------------------------------------------------------------------- Portage 2.0.50-r8 (default-x86-2004.0, gcc-3.3.2, glibc-2.3.2-r9, 2.6.6) ================================================================= System uname: 2.6.6 i686 Pentium III (Coppermine) Gentoo Base System version 1.4.3.13 distcc 2.13 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled] ccache version 2.3 [enabled] Autoconf: sys-devel/autoconf-2.59-r3 Automake: sys-devel/automake-1.8.3 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O2 -march=pentium3 -fomit-frame-pointer -pipe" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -march=pentium3 -fomit-frame-pointer -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache distcc sandbox" GENTOO_MIRRORS="http://gentoo.mirrors.pair.com/ http://mirrors.tds.net/gentoo http://gentoo.seren.com/gentoo http://gentoo.binarycompass.org/ http://gentoo.oregonstate.edu" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://XXXX/gentoo-portage" USE="apm arts avi berkdb crypt cups emacs encode foomaticdb gdbm gif imlib jpeg libg++ libwww mad md5sum mikmod mmx motif mpeg ncurses oggvorbis opengl oss pam pdflib perl png python qt quicktime readline sdl slang spell sse ssl svga tiff truetype x86 xml2 xmms xv zlib" grep DIST /etc/make.conf DISTCC_DIR="${PORTAGE_TMPDIR}/distcc" DISTCC_HOST="XXXX/2"
emerge info -v | grep DIST You might need to have PORTAGE_TMPDIR defined in make.conf if you are going to use a variable expantion like that.
*** This bug has been marked as a duplicate of 51532 ***
