From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:46971) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1duK0m-0005RR-J4 for qemu-devel@nongnu.org; Tue, 19 Sep 2017 11:00:41 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1duK0g-0001W2-Ri for qemu-devel@nongnu.org; Tue, 19 Sep 2017 11:00:32 -0400 Received: from mx1.redhat.com ([209.132.183.28]:61675) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1duK0g-0001Va-LV for qemu-devel@nongnu.org; Tue, 19 Sep 2017 11:00:26 -0400 From: Cornelia Huck Date: Tue, 19 Sep 2017 16:56:32 +0200 Message-Id: <20170919145636.9389-35-cohuck@redhat.com> In-Reply-To: <20170919145636.9389-1-cohuck@redhat.com> References: <20170919145636.9389-1-cohuck@redhat.com> Subject: [Qemu-devel] [PULL 34/38] configure: Allow --enable-seccomp on s390x, too List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: peter.maydell@linaro.org Cc: qemu-devel@nongnu.org, rth@twiddle.net, agraf@suse.de, thuth@redhat.com, borntraeger@de.ibm.com, david@redhat.com, Cornelia Huck From: Thomas Huth 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 Message-Id: <1505385363-27717-1-git-send-email-thuth@redhat.com> Acked-by: Christian Borntraeger Acked-by: Eduardo Otubo Acked-by: Halil Pasic Signed-off-by: Cornelia Huck --- configure | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/configure b/configure index 94db2d103e..cb0f7ed0ab 100755 --- a/configure +++ b/configure @@ -2025,7 +2025,7 @@ if test "$seccomp" != "no" ; then arm|aarch64) libseccomp_minver="2.2.3" ;; - ppc|ppc64) + ppc|ppc64|s390x) libseccomp_minver="2.3.0" ;; *) -- 2.13.5