[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [PATCH v1] xen: preserve COMPAT in CFLAGS
A given Qemu version can not predict what version of Xen it will run on. There are some checks in configure to decide what Xen libraries and functions are available. How exactly these functions must be accessed has to be decided by configure and the user who is compiling Qemu. In no way some random header file must override this decision. Remove the breakage introduced by commit 5eeb39c24b, which would always hide the libxc interfaces the given version of Qemu knows about. The current symptom of such breakage is a build failure with qemu-2.9 and older, in combination with Xen 4.12. Fixes: 5eeb39c24b7d4da5d129bfdd9c4fd21cfb3d28d6 Signed-off-by: Olaf Hering <olaf@xxxxxxxxx> --- include/hw/xen/xen_common.h | 9 --------- 1 file changed, 9 deletions(-) diff --git a/include/hw/xen/xen_common.h b/include/hw/xen/xen_common.h index 5f1402b494..33fa2d3497 100644 --- a/include/hw/xen/xen_common.h +++ b/include/hw/xen/xen_common.h @@ -1,15 +1,6 @@ #ifndef QEMU_HW_XEN_COMMON_H #define QEMU_HW_XEN_COMMON_H -/* - * If we have new enough libxenctrl then we do not want/need these compat - * interfaces, despite what the user supplied cflags might say. They - * must be undefined before including xenctrl.h - */ -#undef XC_WANT_COMPAT_EVTCHN_API -#undef XC_WANT_COMPAT_GNTTAB_API -#undef XC_WANT_COMPAT_MAP_FOREIGN_API - #include <xenctrl.h> #include <xenstore.h> #include <xen/io/xenbus.h> _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxxx https://lists.xenproject.org/mailman/listinfo/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |