From: "Bryan D. Payne" <bryan@thepaynes.cc>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: New release candidate for Xen 3.4.3
Date: Thu, 22 Apr 2010 16:24:52 -0400 [thread overview]
Message-ID: <i2s64bddf0e1004221324x63821697pbfcb13ba9dee7199@mail.gmail.com> (raw)
In-Reply-To: <C7F5CC8C.12145%keir.fraser@eu.citrix.com>
> I hope that this will be the final RC before the 3.4.3 release. Please test!
I'm getting a build error with this RC. I simply did a "make world"
after cloning the repository and end up with the resulting error while
building tools/ioemu-remote/i386-dm:
helper2.c: In function ‘cpu_x86_init’:
helper2.c:150: error: ‘shared_iopage_t’ has no member named ‘vcpu_ioreq’
I've build many other versions of Xen from the source without
problems, so I doubt that this is something unusual with my build
environment. However, in debugging this I did notice that
'shared_iopage_t' is defined in ioreq.h, which has four locations
inside the build tree:
(1) dist/install/usr/include/xen/hvm/ioreq.h
(2) dist/install/lib/modules/2.6.18.8-xen/source/include/xen/interface/hvm/ioreq.h
(3) linux-2.6.18-xen.hg/include/xen/interface/hvm/ioreq.h
(4) tools/include/xen/hvm/ioreq.h
Comparing these, (1) and (4) are the same and (2) and (3) are the
same. The definition of shared_iopage_t in (2) and (3) looks like
this:
struct shared_iopage {
struct ioreq vcpu_ioreq[1];
};
typedef struct shared_iopage shared_iopage_t;
And the definition of shared_iopage_t in (1) and (4) looks like this:
struct shared_iopage {
struct vcpu_iodata vcpu_iodata[1];
};
typedef struct shared_iopage shared_iopage_t;
I'm not sure what's going on here, but it seems like it could be a bug
in the build system. Since this is an RC, I wanted to report it and
see if anyone can comment on why this is happening.
Thanks,
bryan
next prev parent reply other threads:[~2010-04-22 20:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-22 8:51 New release candidate for Xen 3.4.3 Keir Fraser
2010-04-22 20:24 ` Bryan D. Payne [this message]
2010-04-22 20:34 ` Keir Fraser
2010-04-22 20:50 ` Bryan D. Payne
2010-04-22 21:11 ` Keir Fraser
2010-04-28 9:37 ` Ian Jackson
2010-04-28 10:28 ` Ian Jackson
2010-04-28 3:51 ` Keir Fraser
2010-04-28 13:32 ` Ian Jackson
2010-04-22 21:40 ` M A Young
2010-04-23 7:05 ` Keir Fraser
2010-04-28 1:46 ` KUWAMURA Shin'ya
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=i2s64bddf0e1004221324x63821697pbfcb13ba9dee7199@mail.gmail.com \
--to=bryan@thepaynes.cc \
--cc=keir.fraser@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 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).