From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: Xen-devel <xen-devel@lists.xensource.com>
Subject: Fresh ioemu build failing
Date: Wed, 04 Mar 2009 00:59:23 -0800 [thread overview]
Message-ID: <49AE42EB.2030407@goop.org> (raw)
I did a clean pull of tools/ioemu-remote, but its failing to build:
gcc -I. -I.. -I/home/jeremy/hg/xen/unstable/tools/ioemu-dir/target-i386 -I/home/jeremy/hg/xen/unstable/tools/ioemu-dir -MMD -MT pt-msi.o -MP -DNEED_CPU_H -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -I/home/jeremy/hg/xen/unstable/tools/ioemu-dir/tcg -I/home/jeremy/hg/xen/unstable/tools/ioemu-dir/tcg/x86_64 -I/home/jeremy/hg/xen/unstable/tools/ioemu-dir/fpu -I/home/jeremy/hg/xen/unstable//tools/libxc -I/home/jeremy/hg/xen/unstable//tools/xenstore -I/home/jeremy/hg/xen/unstable//tools/include -I/home/jeremy/hg/xen/unstable//tools/blktap/lib -O2 -g -fno-strict-aliasing -Wall -Wundef -Wendif-labels -Wwrite-strings -O1 -fno-omit-frame-pointer -fno-optimize-sibling-calls -m64 -g -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes -Wno-unused-value -Wdeclaration-after-statement -D__XEN_TOOLS__ -MMD -MF .pt-msi.o.d -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -Wno-unused -Wno-declaration-after-statement -Wno-pointer-sign -DCONFIG_PASSTHROUGH -I../hw -m64 -DUSE_SSE2=1 -msse2 -Wno-unused -Wno-declaration-after-statement -Wno-pointer-sign -DCONFIG_PASSTHROUGH -c -o pt-msi.o /home/jeremy/hg/xen/unstable/tools/ioemu-dir/hw/pt-msi.c
/home/jeremy/hg/xen/unstable/tools/ioemu-dir/hw/pt-msi.c: In function 'pt_msi_update':
/home/jeremy/hg/xen/unstable/tools/ioemu-dir/hw/pt-msi.c:130: error: too few arguments to function 'xc_domain_update_msi_irq'
/home/jeremy/hg/xen/unstable/tools/ioemu-dir/hw/pt-msi.c: In function 'pt_msix_update_one':
/home/jeremy/hg/xen/unstable/tools/ioemu-dir/hw/pt-msi.c:307: error: too few arguments to function 'xc_domain_update_msi_irq'
J
next reply other threads:[~2009-03-04 8:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-04 8:59 Jeremy Fitzhardinge [this message]
2009-03-04 9:15 ` Fresh ioemu build failing Keir Fraser
2009-03-04 10:30 ` Ian Jackson
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=49AE42EB.2030407@goop.org \
--to=jeremy@goop.org \
--cc=Ian.Jackson@eu.citrix.com \
--cc=xen-devel@lists.xensource.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 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.