"scanelf: enabling seccomp failed" messages when building packages
When building packages, during the postcheck, binary stripping, shared object scan, and possibly other steps, the message scanelf: enabling seccomp failed
gets printed. This does not seem to cause any issues per se, but I think it nonetheless is worth investigating as it is unexpected and confusing to users.
Edited by Newbyte