Summary: | dev-libs/klibc-1.4.13 sandbox violation | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Dmitry B <icommitter> |
Component: | New packages | Assignee: | Christian Heim (RETIRED) <phreak> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | fbcyborg, gentoo, phajdan.jr |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Dmitry B
2007-05-12 14:52:14 UTC
Same problem here. Looks like a result of this (from the install-section of the ebuild): # Fix the permissions (bug #178053) on /usr/$(get_libdir)/klibc/include/linux # Actually I have no idea, why the includes have those weird-ass permissions # or a particular system, might be due to inherited permissions from parent # directory find /usr/$(get_libdir)/klibc/include/linux -type f | xargs chmod 0644 Ebuild compiles fine without this find-Command. I guess bug #178053 should be opened again. Just committed a fix for this, I introduced w/ fixing #178053 (note to self: always use ${D} as prefix in src_install). *** Bug 178363 has been marked as a duplicate of this bug. *** (In reply to comment #5) > *** Bug 178363 has been marked as a duplicate of this bug. *** > Hello, I'm sorry for the duplicate. Search engine didn't show any result about it, so I opened a new bug report. Anyway.. I tried to do find /usr/$(get_libdir)/klibc/include/linux -type f | xargs chmod 0644 No way to solve my problem.. What's the real solution to that bug? (In reply to comment #6) > (In reply to comment #5) > > *** Bug 178363 has been marked as a duplicate of this bug. *** > > > > Hello, I'm sorry for the duplicate. Search engine didn't show any result about > it, so I opened a new bug report. > > Anyway.. I tried to do find /usr/$(get_libdir)/klibc/include/linux -type f | > xargs chmod 0644 > > No way to solve my problem.. What's the real solution to that bug? > I also tried to do find /usr/$(get_libdir)/klibc/include | xargs chmod o+rX but, I can't fix it as you say. The find command is not the solution but the problem. You don't have to execute it, it is inside the dev-libs/klibc/klibc-1.4.13.ebuild. Comment #4 said a fix is commited, so it should be sufficient to sync your portage again. |