> For nearly everything that it gets used for, libseccomp depends on > CONFIG_SECCOMP_FILTER.
In that case, we're out of luck: Without writing a kernel patch for full seccomp support on these architectures, there won't be a libseccomp2 for them. Should this bug be kept open then? I think it might make sense, because other packages can be pointed here in case they add a hard dependency on libseccomp2 and will then FTBFS on the unsupported archs. Opinions?
