configure: fix seccomp check

Currently, if libseccomp is missing but the user explicitly requested
seccomp support using --enable-seccomp, configure silently ignores the
situation and disables seccomp support.

This is unlike all other tests that explicitly fail in such situation.

Fix that.

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Reviewed-by: Andreas Färber <afaerber@suse.de>
Signed-off-by: Stefan Hajnoczi <stefanha@gmail.com>
(cherry picked from commit e84d5956cc6215d2f098e7b6090fc5ec4cba1be3)

Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>

diff --git a/configure b/configure
index 6f457add6fea9c612baae5b8467cea60bd466b73..61fc8ef4635e1f79b48931fa0e2c10ea94d84555 100755 (executable)
--- a/configure
+++ b/configure
@@ -1395,10 +1395,10 @@ if test "$seccomp" != "no" ; then
         LIBS=`$pkg_config --libs libseccomp`
        seccomp="yes"
     else
-       seccomp="no"
        if test "$seccomp" = "yes"; then
             feature_not_found "libseccomp"
        fi
+       seccomp="no"
     fi
 fi
 ##########################################