The emerging of kile-1.4 never completes due to some "access violation". In other words it tries to make a directory in my home directory, namely ~/.kde3. Is the ebuild trying to do the right thing? And if yes, do I need to change somehow my FEATURES settings (which I suspect are the reason it aborts)? I'd prefer not to, though, and have the ebuild working properly with them :-) Reproducible: Always Steps to Reproduce: 1. set FEATURES="sandbox buildpkg ccache userpriv usersandbox" in /etc/make.conf 2. emerge kile 3. Actual Results: The ebuild exited with the error --------------------------- ACCESS VIOLATION SUMMARY --------------------------- LOG FILE = "/tmp/sandbox-kile-1.4-26488.log" mkdir: /home/gek/.kde3 mkdir: /home/gek/.kde3 mkdir: /home/gek/.kde3 mkdir: /home/gek/.kde3 mkdir: /home/gek/.kde3 mkdir: /home/gek/.kde3 -------------------------------------------------------------------------------- Portage 2.0.47-r10 (default-x86-1.4, gcc-3.2.2, glibc-2.3.1-r2) ================================================================= System uname: 2.4.19-gentoo-r10 i686 AMD Athlon(tm) Processor GENTOO_MIRRORS="ftp://ftp.ntua.gr/pub/linux/gentoo http://gentoo.oregonstate.edu/ http://www.ibiblio.org/pub/Linux/distributions/gentoo" 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" PORTDIR="/usr/portage" DISTDIR="/usr/portage/distfiles" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR_OVERLAY="/usr/local/portage" USE="x86 oss 3dnow apm avi crypt cups encode gif jpeg libg++ mikmod mmx mpeg ncurses nls pdflib png quicktime spell truetype xml2 xmms xv zlib gdbm berkdb slang readline arts svga java X sdl gpm tcpd pam libwww ssl python imlib oggvorbis gtk qt kde motif opengl -alsa cdr dga doc dvd fbcon -gnome imap maildir mysql perl samba scanner sse tcltk tetex tiff wmf" COMPILER="gcc3" CHOST="i686-pc-linux-gnu" CFLAGS="-march=athlon-tbird -O3 -pipe -fomit-frame-pointer" CXXFLAGS="-march=athlon-tbird -O3 -pipe -fomit-frame-pointer" ACCEPT_KEYWORDS="x86" MAKEOPTS="-j2" AUTOCLEAN="yes" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage/" FEATURES="sandbox buildpkg ccache userpriv usersandbox"
Are you running portage as root, as user, sudoing as root, suing to root, or what?
I am running it as root from konsole. In my konsole settings, the "Root Console" session is initiated by executing "su -".
Although my previous comment says that I am running root executing "su -", it seems that this was not the case eventually. I opened up a new konsole session with "su -", and kile emerged succesfully. I should note, though, that the session that gave me problems with kile has been used numerous times for emerging packages, without any access violation problems. Oh, well...
So you can't reproduce this anymore? If so, please close the bugreport (since I couldn't reproduce it to begin with).
I suppose I could reprodyce it if I tried. Perhaps by doing a plain "su" before emerging, thus leaving $USER to be a user other than root. Anyway, this was not really a bug with the ebuild, so I am resolving it to INVALID
