Summary: | www-client/chromium-27.0.1453.65 fails to build with selinux use-flag disabled | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Dominik Kriegner <dominik.kriegner> |
Component: | Current packages | Assignee: | Chromium Project <chromium> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
build log
proposed patch |
Description
Dominik Kriegner
2013-04-30 07:33:53 UTC
Created attachment 346950 [details]
build log
I stumbled accross this problem because chromium was not usable with selinux (in permissive mode) without starting it with chromium --no-sandbox (as suggested in bug #465574 content/zygote/zygote_main_linux.cc: In function ‘bool content::EnterSandbox(sandbox::SetuidSandboxClient*, bool*, bool*)’: content/zygote/zygote_main_linux.cc:442:61: error: expected ‘;’ before ‘)’ token Created attachment 346964 [details, diff]
proposed patch
using this patch i could successfully build chromium with use flag selinux disabled
I think this is completely broken and unmaintained upstream. Removed. 01 May 2013; Pawel Hajdan jr chromium-27.0.1453.65.ebuild, chromium-28.0.1490.2.ebuild, chromium-9999-r1.ebuild: Disable unmaintained upstream SELinux mode, bug #465574 by swift, bug #467954 by Dominik Kriegner. Thank you for the patch by the way. I think it's good and it works - however, there are other problems with this way of SELinux sandboxing, see the other bug above. If anyone is interested in making it work upstream, I can help review changes. |