Closed thesamesam closed 2 years ago
Ugh, well that's surprising to me. But perfectly documented.
This also means that if seccomp libraries are present and configure is given --disable-seccomp
, it'll both be enabled and defaulted to on (DEFAULT_SECCOMP
).
Do you want to fix that, or should I merge this and do that party myself?
The first branch ("[action-if-given]") is taken even if --disable-seccomp is passed. So, in that branch, check whether the user disabled it or not.
Without this, we'd get a failure when seccomp is detected but we want to disable it:
Signed-off-by: Sam James sam@gentoo.org