I'm trying to emerge the Qt module for Perl : $ emerge dev-perl/PerlQt This ends with the following error: ... Good - your configure finished. Start make now >>> Source unpacked. --------------------------- ACCESS VIOLATION SUMMARY --------------------------- LOG FILE = "/tmp/sandbox-dev-perl_-_PerlQt-3.008-1955.log" open_wr:
I'm trying to emerge the Qt module for Perl : $ emerge dev-perl/PerlQt This ends with the following error: ... Good - your configure finished. Start make now >>> Source unpacked. --------------------------- ACCESS VIOLATION SUMMARY --------------------------- LOG FILE = "/tmp/sandbox-dev-perl_-_PerlQt-3.008-1955.log" open_wr: /usr/qt/3/etc/settings/.qtrc.lock open_wr: /usr/qt/3/etc/settings/.qtrc.lock -------------------------------------------------------------------------------- Reproducible: Always Steps to Reproduce: 1. 2. 3. $ FEATURES="-sandbox" emerge PerlQt did install the package
I can't duplicate this on this end (emerges fine). Do you have any special FEATURES set in your make.conf? (userprivs, etc.)
Nothing special in my make.conf. Here it is: # These settings were set by the catalyst build script that automatically built this stage # Please consult /etc/make.conf.example for a more detailed example CFLAGS="-O2 -march=i686 -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CXXFLAGS="${CFLAGS}" MAKEOPTS="-j2" USE="qt kde alsa lirc oss mmx -gnome -gtk" ALSA_CARDS="intel8x0" GENTOO_MIRRORS="http://ftp.gentoo-pt.org/pub/gentoo http://ftp.du.se/pub/os/gentoo http://mirror.gentoo.ru/pub/mirror/gentoo/"
adding an addwrite $QTDIR/etc/settings to src_compile should fix the sandbox error
I get the same problem with the sandbox violation. I looked in the ebuild, but there is no src_compile function to put the addwrite statement in. I tried putting it in both the src_unpack function which allowed it to get past the violation, but then the configure script ran twice before ving the same sandbox violation. Finally, I tried putting the addwrite statement in the src_install function. Now the system compiles, but it still won't install without that error. I'm half tempted to disable the sandbox, but the script seems to be misbehaving and I don't want it to go nuts on my system.
Shouldn't this bug's component be listed as "ebuilds" instead of "development"?
.8-r1 in portage now. tested heavily, no more sandbox violations. Enjoy :)