As I recently learned, CONFIG_SECCOMP's default value is "y", and this can
cause the build to fail until the remaining bits of this feature are
committed. The attached patch changes the default to "n".
"Such is oft the course of deeds that move the wheels of the world: small
hands do them because they must, while the eyes of the great are elsewhere."
--- arch/mips/Kconfig.orig 2005-03-21 14:31:08.757419840 -0500
+++ arch/mips/Kconfig 2005-03-21 14:31:20.955565440 -0500
@@ -1422,7 +1422,7 @@ config BINFMT_ELF32
bool "Enable seccomp to safely compute untrusted bytecode"
depends on PROC_FS && BROKEN
- default y
+ default n
This kernel feature is useful for number crunching applications
that may need to compute untrusted bytecode during their