Summary: | media-tv/mythtv-0.21_p19961-r2 - sandbox violation of /etc/ld.so.cache~ | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Keith Harrison <KeithBHarrison> |
Component: | Current packages | Assignee: | Doug Goldstein (RETIRED) <cardoe> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | bpenglase, candrews, danza.vera, hirakendu, iaindb, media-tv, per, saintdev |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | patch to compile mythtv (0.22-svn-r20677) with sandbox-2.0 |
Description
Keith Harrison
2009-06-06 01:17:43 UTC
The fun part is when you realize that it its actually the new ieee1394 library that is causing the sandbox violation. I just changed the use flag for mythtv since I don't actually use it with a cable box via ieee1394. It built fine and I once again have a functional mythtv. (In reply to comment #1) > The fun part is when you realize that it its actually the new ieee1394 library > that is causing the sandbox violation. I just changed the use flag for mythtv > since I don't actually use it with a cable box via ieee1394. It built fine and > I once again have a functional mythtv. > I tried USE="-ieee1394" emerge mythtv this morning and it gave me the same error. (In reply to comment #2) > (In reply to comment #1) > > The fun part is when you realize that it its actually the new ieee1394 library > > that is causing the sandbox violation. I just changed the use flag for mythtv > > since I don't actually use it with a cable box via ieee1394. It built fine and > > I once again have a functional mythtv. > > > > I tried USE="-ieee1394" emerge mythtv this morning and it gave me the same > error. > Oh, you are correct, I forgot exactly what it was. I had to do FEATURES=-sandbox USE=-ieee1394 emerge mythtv. So, the ieee1394 part wasn't causing the sandbox violation. I tried emerging with FEATURES=-sandbox and having ieee1394 still in my use flags. somehow that didn't work. But taking both out of the equation not only let me build but the program was usable after that. hooray. I have attached a patch to fix it. Strangely, a usual fix of not doing ldconfig by export LDCONFIG=/bin/true did not work in this case. And it turned out to be a somewhat tricky package to figure out where ldconfig is being called. Note that the problem comes up apparently after an update from sandbox-1.9 to 2.0. Created attachment 193831 [details, diff]
patch to compile mythtv (0.22-svn-r20677) with sandbox-2.0
Apart from adding this patch to files/ folder, add this to ebuild in src_unpack (or src_prepre):
# sandbox-2.0:
cd "${S}"
epatch ${FILESDIR}/${PN}-sandbox.patch
Patch works for me... (In reply to comment #6) > Patch works for me... > Confirmed, patch working for me too. ~AMD64, sandbox 2.0, Portage 2.1.6.13 (default/linux/amd64/2008.0/desktop, gcc-4.3.3, glibc-2.10.1-r0, 2.6.30-rc7-zen0-0-08384-gce1adbc x86_64) (In reply to comment #5) > Created an attachment (id=193831) [edit] > patch to compile mythtv (0.22-svn-r20677) with sandbox-2.0 > > Apart from adding this patch to files/ folder, add this to ebuild in src_unpack > (or src_prepre): > # sandbox-2.0: > cd "${S}" > epatch ${FILESDIR}/${PN}-sandbox.patch > I confirm that I too ran in to this issue for the same reasons listed above, and this patch applied to the ebuild in question with the file in the proper files/ subfolder and then an ebuild manifest (just to make sure), resulted in a properly installed mythtv. I can also confirm that this is -not- http://bugs.gentoo.org/show_bug.cgi?id=240530 , which I found when I ran in to this again after I decided to rebuild, instead of copy, the gentoo install on the new root. I get the same sandbox violation when compiling mythtv-0.21_p20877 (In reply to comment #10) > I get the same sandbox violation when compiling mythtv-0.21_p20877 > mythtv-0.21_p20877 compiles and installs fine with the above mythtv-sandbox.patch. Thanks for the patch. Fixed. |