Trying to emerge net-im/sim-0.9.3-r2 I get a message saying access violation This is the exactlog message (over 1k lines of the same messages as shown here, so can't paste the entire log from the beginning): open_wr: /usr/qt/3/etc/settings/qt_plugins_3.3rc.tmp open_wr: /usr/qt/3/etc/settings/.qtrc.lock open_wr: /usr/qt/3/etc/settings/.qt_plugins_3.3rc.lock Note: I've trimmed the above log to show what files are affected, the same takes over 1k lines in the log self. Reproducible: Always Steps to Reproduce: 1. # emerge -v =net-im/sim-0.9.3-r2 2. wait some time 3. read the log Actual Results: Exactly what is described in Details happens every time I try to merge this version if net-im/sim Expected Results: I expect that it actually installs without trying to open those .lock files in wr mode (if I understand the log messages right). emerge info: Portage 2.0.50-r6 (default-x86-1.4, gcc-3.3.2, glibc-2.3.3_pre20040207-r0, 2.6.5-love4) ================================================================= System uname: 2.6.5-love4 i686 Intel(R) Pentium(R) 4 CPU 3.20GHz Gentoo Base System version 1.4.8 Autoconf: sys-devel/autoconf-2.59-r3 Automake: sys-devel/automake-1.8.3 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-O2 -march=pentium4 -fprefetch-loop-arrays -funroll-loops -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.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="-O2 -march=pentium4 -fprefetch-loop-arrays -funroll-loops -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache sandbox" GENTOO_MIRRORS="http://linux.rz.ruhr-uni-bochum.de/download/gentoo-mirror/" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage /home/portage /home/portage/overlay-freedesktop /usr/local/portage/bmg-gnome-current" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="X aalib alsa apache2 apm arts avi berkdb bonobo cdr crypt cups directfb dvd encode esd firebird flash foomaticdb gdbm gif gnome gnutls gphoto2 gpm gtk gtk2 gtkhtml imlib java jpeg kde libg++ libwww mad mikmod mmx motif mozilla moznocompose moznoirc moznomail mozxmlterm mpeg mysql nas ncurses nls nptl nvidia oggvorbis opengl oss pam pdflib perl php png python qt quicktime readline ruby samba scanner sdl slang spell sse ssl svga tcltk tcpd tetex tiff truetype x86 xchattext xml xml2 xmms xv zlib"
Created attachment 29312 [details, diff] The diff between two ebuilds Here the attachment of the difference between the two ebuilds of sim (revision 1 to revision 2). I haven't tried modifying the ebuild according to the patch, but it might help adding the following back (see the diff): -if [ $( use kde ) ]; then - inherit kde-base eutils - need-kde 3 -else - inherit base kde-functions eutils - need-qt 3 -fi
Created attachment 29321 [details] The working ebuild This is the modified ebuild for revision 2 with some sources from revision 1. This one works.
Created attachment 29323 [details, diff] Diff between the one in Portage tree and my modification of it This modification is, however, purely based on the ebuild of net-im/sim-0.9.3-r1 in Portage tree.
Just want to say that I have the same exact error. Haven't tried the patch thought.
Simply take the ebuild supplied in comment #2. To be honest, though, there's no source difference between the 2 revisions. That's only the revision of the ebuild (no additional patches and similar, only new deps and the ebuild self got rewritten) - talking of the official -r2 in Portage tree.
Had the same problem, but this did the trick: FEATURES="-sandbox" ACCEPT_KEYWORDS="~x86" emerge sim
@#6: Sure it lets you compile that but what's the purpose of sandbox, if you have to disable it, then? :)
@NeoNik: I still wonder the same. Heard that OpenOffice hav had problems with it too. Maybe someone should investigate (I don't have the time and knowledge).
