configure.ac: define HAVE_SECCOMP macro when using seccomp, fix build/tests

Happily the failing tests should prevent anyone from using such a Nix
in situations where they expect sandboxing to be on,
which would otherwise be a risk.
This commit is contained in:
Will Dietz 2018-02-19 12:13:51 -06:00
parent 623fcb071e
commit a6c0b773b7

View file

@ -196,6 +196,7 @@ if test "$sys_name" = linux; then
PKG_CHECK_MODULES([LIBSECCOMP], [libseccomp], PKG_CHECK_MODULES([LIBSECCOMP], [libseccomp],
[CXXFLAGS="$LIBSECCOMP_CFLAGS $CXXFLAGS"]) [CXXFLAGS="$LIBSECCOMP_CFLAGS $CXXFLAGS"])
have_seccomp=1 have_seccomp=1
AC_DEFINE([HAVE_SECCOMP], [1], [Whether seccomp is available and should be used for sandboxing.])
else else
have_seccomp= have_seccomp=
fi fi