Summary: | sys-apps/busybox-1.20.1 fails with sandboxing enabled | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Walther <walther.md> |
Component: | Sandbox | Assignee: | Sandbox Maintainers <sandbox> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Walther
2012-06-17 21:11:49 UTC
is your make built with USE=static ? No, I don't use "static" unless needed. However, after re-emerging make with USE="static", busybox manages to compile just fine. What does that mean, though? Should "make" be compiled with "static" in order to use sandboxing? Or is it a bug (or limitation) of the the sandbox lib? sys-devel/make-3.82-r3 sys-apps/busybox-1.20.2 (In reply to comment #2) the opposite -- make should be built with USE=-static i don't know why this is failing ... no one else has reported this before ... is this still an issue with the latest busybox & sandbox versions ? (In reply to SpanKY from comment #4) > is this still an issue with the latest busybox & sandbox versions ? Nope, it compiles/installs fine now. No idea when/how/why it got fixed. FEATURES="userfetch userpriv usersandbox parallel-fetch" sys-apps/busybox-1.23.1-r1 ipv6 pam -debug -livecd -make-symlinks -math -mdev -savedconfig (-selinux) -sep-usr -static -syslog -systemd sys-devel/make-4.1 nls -guile -static |