diff options
| author | dann frazier <dann.frazier@canonical.com> | 2015-10-23 15:34:22 -0600 |
|---|---|---|
| committer | Eduardo Otubo <eduardo.otubo@profitbricks.com> | 2015-11-16 09:49:47 +0100 |
| commit | ba060c53d585d186ff0ac6b181f4b2a867acc210 (patch) | |
| tree | b2da7e141d1ca6fff55cf71eaa4fa38ba1f803f2 /configure | |
| parent | 693e59105d2ce4d6f4c96a2373fec06a24d0e6be (diff) | |
| download | qemu-ba060c53d585d186ff0ac6b181f4b2a867acc210.zip | |
seccomp: loosen library version dependency
Drop the libseccomp required version back to 2.1.0, restoring the ability
to build w/ --enable-seccomp on Ubuntu 14.04.
Commit 4cc47f8b3cc4f32586ba2f7fce1dc267da774a69 tightened the dependency
on libseccomp from version 2.1.0 to 2.1.1. This broke building on Ubuntu
14.04, the current Ubuntu LTS release. The commit message didn't mention
any specific functional need for 2.1.1, just that it was the most recent
stable version at the time. I reviewed the changes between 2.1.0 and 2.1.1,
but it looks like that update just contained minor fixes and cleanups - no
obvious (to me) new interfaces or critical bug fixes.
Signed-off-by: dann frazier <dann.frazier@canonical.com>
Acked-by: Eduardo Otubo <eduardo.otubo@profitbricks.com>
Diffstat (limited to 'configure')
| -rwxr-xr-x | configure | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -1890,7 +1890,7 @@ fi if test "$seccomp" != "no" ; then case "$cpu" in i386|x86_64) - libseccomp_minver="2.1.1" + libseccomp_minver="2.1.0" ;; arm|aarch64) libseccomp_minver="2.2.3" |