Re: [Xen-devel] [PATCH v1] xen: preserve COMPAT in CFLAGS

[Anthony PERARD <anthony.perard@xxxxxxxxxx>]

On Fri, Oct 26, 2018 at 12:10:16PM +0200, Olaf Hering wrote:
> 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.

I can't reproduce this build issue.

I've build QEMU 2.9.1 against Xen 4.11, and it build just fine. (I just
needed -DXC_WANT_COMPAT_DEVICEMODEL_API).
But when building againt unstable (to be 4.12), it's configure that
fails. That patch would not work.

Could you tell me a configuration of QEMU and Xen that fails? Their
versions, or theirs commit id.
And can you attach the output of ./configure, as well as the build
failures?


As for 
https://lists.xenproject.org/archives/html/xen-devel/2018-10/msg01950.html
It appear that the same QEMU 2.9.1 is used, but QEMU isn't supposed to
use the function xc_map_foreign_bulk when built against Xen 4.12. That
function is only supposed to be used when building against Xen 4.6 and
earlier.  QEMU 2.9.1 knows about Xen up to 4.8, it should have used
xenforeignmemory_map directly. So, this is probably an issue with
./configure.

Thanks,

-- 
Anthony PERARD

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel