From: "Michael S. Tsirkin" <mst@redhat.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: ehabkost@redhat.com, qemu-devel@nongnu.org,
paul.durrant@citrix.com, pbonzini@redhat.com, "Chen,
Tiejun" <tiejun.chen@intel.com>,
rth@twiddle.net
Subject: [Qemu-devel] qemu build fails on xen
Date: Tue, 7 Jul 2015 11:45:29 +0300 [thread overview]
Message-ID: <20150707114036-mutt-send-email-mst@redhat.com> (raw)
The following error triggers on Fedora 22:
In file included from /scm/qemu/include/hw/xen/xen_backend.h:4:0,
from hw/block/xen_disk.c:39:
/scm/qemu/include/hw/xen/xen_common.h:198:18: error: conflicting types for ‘ioservid_t’
typedef uint32_t ioservid_t;
^
In file included from /usr/include/xen/hvm/params.h:24:0,
from /usr/include/xenctrl.h:46,
from /scm/qemu/include/hw/xen/xen_common.h:9,
from /scm/qemu/include/hw/xen/xen_backend.h:4,
from hw/block/xen_disk.c:39:
/usr/include/xen/hvm/hvm_op.h:255:18: note: previous declaration of ‘ioservid_t’ was here
typedef uint16_t ioservid_t;
^
/scm/qemu/rules.mak:57: recipe for target 'hw/block/xen_disk.o' failed
make: *** [hw/block/xen_disk.o] Error 1
make: *** Waiting for unfinished jobs....
Reverting 3996e85c1822e05c50250f8d2d1e57b6bea1229d
Author: Paul Durrant <paul.durrant@citrix.com>
Date: Tue Jan 20 11:06:19 2015 +0000
Xen: Use the ioreq-server API when available
Looking at that header:
#ifndef HVM_PARAM_BUFIOREQ_EVTCHN
#define HVM_PARAM_BUFIOREQ_EVTCHN 26
#endif
#define IOREQ_TYPE_PCI_CONFIG 2
typedef uint32_t ioservid_t;
Are all polluting the global namespace, not to mention, violate the coding
style. Why not prefix them with Xen_, xen_ etc?
--
MST
next reply other threads:[~2015-07-07 8:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-07 8:45 Michael S. Tsirkin [this message]
2015-07-07 8:48 ` [Qemu-devel] qemu build fails on xen Michael S. Tsirkin
2015-07-07 9:26 ` Paul Durrant
2015-07-07 12:37 ` Peter Maydell
2015-07-07 13:12 ` Paul Durrant
2015-07-07 13:26 ` Paul Durrant
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=20150707114036-mutt-send-email-mst@redhat.com \
--to=mst@redhat.com \
--cc=ehabkost@redhat.com \
--cc=paul.durrant@citrix.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=stefano.stabellini@eu.citrix.com \
--cc=tiejun.chen@intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).