From a6c0b773b72d4e30690e01f1f1dcffc28f2d9ea1 Mon Sep 17 00:00:00 2001 From: Will Dietz Date: Mon, 19 Feb 2018 12:13:51 -0600 Subject: [PATCH] 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. --- configure.ac | 1 + 1 file changed, 1 insertion(+) diff --git a/configure.ac b/configure.ac index 4102f3216..54322d463 100644 --- a/configure.ac +++ b/configure.ac @@ -196,6 +196,7 @@ if test "$sys_name" = linux; then PKG_CHECK_MODULES([LIBSECCOMP], [libseccomp], [CXXFLAGS="$LIBSECCOMP_CFLAGS $CXXFLAGS"]) have_seccomp=1 + AC_DEFINE([HAVE_SECCOMP], [1], [Whether seccomp is available and should be used for sandboxing.]) else have_seccomp= fi