config: rename SECCOMP to USE_SECCOMP
authorRobert Marko <robimarko@gmail.com>
Sat, 23 Nov 2024 13:29:49 +0000 (14:29 +0100)
committerFelix Fietkau <nbd@nbd.name>
Fri, 3 Jan 2025 10:18:56 +0000 (11:18 +0100)
commit184d1c93cbe47e70c8bb4b01ddf7dc9152a58e23
treea9914789407633e4f3afaade3f5c56b3edded88a
parent933ae0699ae61b1e841c08ffe41aa7eea0ca673d
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>
(cherry picked from commit a48ec449ccab0069e84a72837bf06ba543e53aec)
config/Config-build.in
package/base-files/Makefile
package/system/procd/Makefile