| commit | 3aa35fcffcf0fe22ac48d4277ed6057ae3e57ce0 | |
| author | Thomas Huth <thuth@redhat.com> | |
| Thu, 14 Sep 2017 10:36:03 +0000 (14 12:36 +0200) | ||
| committer | Cornelia Huck <cohuck@redhat.com> | |
| Tue, 19 Sep 2017 16:31:32 +0000 (19 18:31 +0200) | ||
| tree | 615d50f7762ed15cf06942c5aae1f5131a525571 | treesnapshot (tar.gz zip) |
| parent | 5ef5475868d00f506699712c1569f10eaa7534a6 | commitdiff |
configure: Allow --enable-seccomp on s390x, too
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 <thuth@redhat.com>
Message-Id: <1505385363-27717-1-git-send-email-thuth@redhat.com>
Acked-by: Christian Borntraeger <borntraeger@de.ibm.com>
Acked-by: Eduardo Otubo <otubo@redhat.com>
Acked-by: Halil Pasic <pasic@linux.vnet.ibm.com>
Signed-off-by: Cornelia Huck <cohuck@redhat.com>
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 <thuth@redhat.com>
Message-Id: <1505385363-27717-1-git-send-email-thuth@redhat.com>
Acked-by: Christian Borntraeger <borntraeger@de.ibm.com>
Acked-by: Eduardo Otubo <otubo@redhat.com>
Acked-by: Halil Pasic <pasic@linux.vnet.ibm.com>
Signed-off-by: Cornelia Huck <cohuck@redhat.com>
| configure | diffblobblamehistory |