config: rename SECCOMP to USE_SECCOMP
authorRobert Marko <robimarko@gmail.com>
Sat, 23 Nov 2024 13:29:49 +0000 (14:29 +0100)
committerRobert Marko <robimarko@gmail.com>
Sun, 24 Nov 2024 11:18:21 +0000 (12:18 +0100)
commita48ec449ccab0069e84a72837bf06ba543e53aec
tree009b054e390bc3617fb08e7488678efd94e457fb
parentfaf4b3e0f7a583a8fa1a65b302ac74457e48575f
config: rename SECCOMP to USE_SECCOMP

It seems that we have some kind of a symbol name conflict which causes
CONFIG_SECCOMP to always be read as y.

Unfortunatelly, I could not figure out what is causing this, but simply
renaming SECCOMP to USE_SECCOMP seems to properly work and leaves the
symbol unset unless arch dependencies are satisfied.

This fixes qoriq and others that dont support seccomp from failing due
to procd-seccomp package being selected to get included but it cannot be
built for them:
ERROR: unable to select packages:
  procd-seccomp (no such package):
    required by: base-files-1637~52b6c92479[procd-seccomp]

Fixes: 4c65359af49b ("build: fix including busybox, procd and apk/opkg in imagebuilder")
Link: https://github.com/openwrt/openwrt/pull/17048
Signed-off-by: Robert Marko <robimarko@gmail.com>
config/Config-build.in
include/toplevel.mk
package/base-files/Makefile
package/system/procd/Makefile