All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: xen-devel@lists.xen.org
Subject: usage of libxc compat function fails with staging
Date: Thu, 25 Oct 2018 14:08:08 +0200	[thread overview]
Message-ID: <20181025140808.13eefc21.olaf@aepfle.de> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 842 bytes --]

I have a matrix of various qemu.git#stable-x.y that build against xen.git#staging*. Since some months qemu.git#stable-2.x fails to build against xen.git#staging. qemu-2.10+ works with staging. To me it is not clear how to fix this failure:

qemu-2.9-20170907T112512.4cd42653f5/include/hw/xen/xen_common.h:61:16: warning: implicit declaration of function 'xc_map_foreign_bulk'

qemu is built with the various compat flags like :-DXC_WANT_COMPAT_MAP_FOREIGN_API=1. I think this should give access to that function. But for some reason the missing function is wrapped further in xenctrl_compat.h.

Is qemu-2.x supposed to define XC_BUILDING_COMPAT_MAP_FOREIGN_API? Commit 3248691679 ("tools: Refactor foreign memory mapping into libxenforeignmemory") in xen.git indicates that just XC_WANT_COMPAT_MAP_FOREIGN_API would be needed.

Olaf

[-- Attachment #1.2: Digitale Signatur von OpenPGP --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 157 bytes --]

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

             reply	other threads:[~2018-10-25 12:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-25 12:08 Olaf Hering [this message]
2018-10-26  9:37 ` usage of libxc compat function fails with staging Olaf Hering

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20181025140808.13eefc21.olaf@aepfle.de \
    --to=olaf@aepfle.de \
    --cc=xen-devel@lists.xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.