From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:49832) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dsRVL-0005Ar-Bb for qemu-devel@nongnu.org; Thu, 14 Sep 2017 06:36:20 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dsRVG-00053I-D6 for qemu-devel@nongnu.org; Thu, 14 Sep 2017 06:36:19 -0400 Received: from mx1.redhat.com ([209.132.183.28]:33572) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1dsRVG-00051g-7N for qemu-devel@nongnu.org; Thu, 14 Sep 2017 06:36:14 -0400 From: Thomas Huth Date: Thu, 14 Sep 2017 12:36:03 +0200 Message-Id: <1505385363-27717-1-git-send-email-thuth@redhat.com> Subject: [Qemu-devel] [PATCH] configure: Allow --enable-seccomp on s390x, too List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org, Cornelia Huck , Christian Borntraeger Cc: David Hildenbrand , Claudio Imbrenda , Dong Jia Shi , Farhan Ali , Halil Pasic , Jason J Herne , Pierre Morel , Eduardo Otubo , Christian Ehrhardt libseccomp supports s390x since version 2.3.0, and I was able to start a VM with "-sandbox on" without any obvious problems by using this patch, so it should be safe to allow --enable-seccomp on s390x nowadays, too. Signed-off-by: Thomas Huth --- configure | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/configure b/configure index fd7e3a5..83ba64e 100755 --- a/configure +++ b/configure @@ -2032,7 +2032,7 @@ if test "$seccomp" != "no" ; then arm|aarch64) libseccomp_minver="2.2.3" ;; - ppc|ppc64) + ppc|ppc64|s390x) libseccomp_minver="2.3.0" ;; *) -- 1.8.3.1