diff options
| author | Michal Privoznik <mprivozn@redhat.com> | 2015-07-10 17:32:00 +0300 |
|---|---|---|
| committer | Dmitry Guryanov <dguryanov@parallels.com> | 2015-07-13 19:46:10 +0300 |
| commit | 541a99cc8a8bfc40212e7ca8d44cad2472b01d3c (patch) | |
| tree | 8ce74c58a97c9cb4586ef9cbb9fbf9d691a6defe /m4/virt-driver-vz.m4 | |
| parent | 09040915c550b045b5c7f11a79c33ca70fee58a2 (diff) | |
| download | libvirt-541a99cc8a8bfc40212e7ca8d44cad2472b01d3c.tar.gz | |
virt-driver-vz: Require parallels-7.0.22 at least
With the latest patch to the vz driver (7d73ca06cefe) I was
getting some compilation errors. It turned out, my installation
of the parallels SDK was not as fresh as it could be. Parallels
installed in my system were missing the
PRL_USE_VNET_NAME_FOR_BRIDGE_NAME symbol which simply was not
introduced at the time I was installing the SDK. The symbol was
introduced in 86e62a5d which was then part of the 7.0.22 release.
Require that version at least therefore.
Signed-off-by: Michal Privoznik <mprivozn@redhat.com>
Diffstat (limited to 'm4/virt-driver-vz.m4')
| -rw-r--r-- | m4/virt-driver-vz.m4 | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/m4/virt-driver-vz.m4 b/m4/virt-driver-vz.m4 index 704976ebd4..67001dce50 100644 --- a/m4/virt-driver-vz.m4 +++ b/m4/virt-driver-vz.m4 @@ -25,7 +25,7 @@ AC_DEFUN([LIBVIRT_DRIVER_CHECK_VZ],[ if test "$with_vz" = "yes" || test "$with_vz" = "check"; then - PKG_CHECK_MODULES([PARALLELS_SDK], [parallels-sdk], + PKG_CHECK_MODULES([PARALLELS_SDK], [parallels-sdk >= $PARALLELS_SDK_REQUIRED], [PARALLELS_SDK_FOUND=yes], [PARALLELS_SDK_FOUND=no]) if test "$with_vz" = "yes" && test "$PARALLELS_SDK_FOUND" = "no"; then |