aboutsummaryrefslogtreecommitdiffstats
path: root/include/unpack.mk
diff options
context:
space:
mode:
authorFlorian Eckert <fe@dev.tdt.de>2021-10-15 09:19:12 +0200
committerDaniel Golle <daniel@makrotopia.org>2021-10-16 02:00:47 +0100
commitb118efa0d25f5b60226a9d316eb838dd6be22f78 (patch)
tree1d0b389ed08221855d4d22e1897108d8a0e032af /include/unpack.mk
parent3a93704a63cf018187411108d241c35ec83992c0 (diff)
downloadupstream-b118efa0d25f5b60226a9d316eb838dd6be22f78.tar.gz
upstream-b118efa0d25f5b60226a9d316eb838dd6be22f78.tar.bz2
upstream-b118efa0d25f5b60226a9d316eb838dd6be22f78.zip
buildsystem: add CONFIG_SECCOMP
Until now, this feature was switched on via the kernel configuration option KERNEL_SECCOMP. The follwing change a7f794cd2aa104fdbd4c6e38f9b76373bf9b96e1 now requires that the package procd-seccomp must also enabled for buildinmg. However, this is not the case we have no dependency and the imagebuilder cannot build the image, because of the implicit package selection. This change adds a new configuration option CONFIG_SECCOMP. The new option has the same behaviour as the configuration option CONFIG_SELINUX. If the CONFIG_SECCOMP is selected then the package procd-seccomp and KERNEL_SECCOMP is enabled for this build. Signed-off-by: Florian Eckert <fe@dev.tdt.de> Signed-off-by: Daniel Golle <daniel@makrotopia.org>
Diffstat (limited to 'include/unpack.mk')
0 files changed, 0 insertions, 0 deletions