First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 53359
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Perl Devs @ Gentoo <perl@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Matthias <matthias.gallant@pandora.be>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 53359 depends on: Show dependency tree
Bug 53359 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2004-06-08 15:38 0000 
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:

------- Comment #1 From Matthias 2004-06-08 15:38:12 0000 ------- 
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

------- Comment #2 From Michael Cummings (RETIRED) 2004-06-13 12:03:15 0000 ------- 
I can't duplicate this on this end (emerges fine). Do you have any special
FEATURES set in your make.conf? (userprivs, etc.)

------- Comment #3 From Matthias 2004-06-13 14:11:54 0000 ------- 
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/"

------- Comment #4 From Caleb Tennis 2004-06-14 08:37:39 0000 ------- 
adding an

addwrite $QTDIR/etc/settings to src_compile

should fix the sandbox error

------- Comment #5 From byte smythe 2004-09-19 10:32:34 0000 ------- 
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.

------- Comment #6 From byte smythe 2004-09-19 17:05:34 0000 ------- 
Shouldn't this bug's component be listed as "ebuilds" instead of "development"?

------- Comment #7 From Michael Cummings (RETIRED) 2004-10-02 16:57:32 0000 ------- 
.8-r1 in portage now. tested heavily, no more sandbox violations. Enjoy :)
First Last Prev Next    No search results available      Search page      Enter new bug