From: Hollis Blanchard <hollisb@us.ibm.com>
To: Avi Kivity <avi@redhat.com>
Cc: kvm@vger.kernel.org, kvm-ppc@vger.kernel.org,
kvm-ia64 <kvm-ia64@vger.kernel.org>
Subject: Re: powerpc kvm-userspace build fixes
Date: Wed, 03 Dec 2008 13:03:36 -0600 [thread overview]
Message-ID: <1228331016.10084.30.camel@localhost.localdomain> (raw)
In-Reply-To: <49366813.9090708@redhat.com>
On Wed, 2008-12-03 at 13:05 +0200, Avi Kivity wrote:
> Hollis Blanchard wrote:
> > I'm also seeing a build dependency issue with dyngen-opc.h that I don't see
> > upstream. I haven't sorted that out yet, but "make qemu/ppcemb-softmmu/dyngen-opc.h" first works around the problem.
> >
>
> Doesn't for me...
I'll send the fix in a separate mail.
Looks like we missed the addition of a dependency from upstream, which
we probably didn't get because it conflicted with the
--disable-cpu-emulation patch in kvm-userspace.
PowerPC stopped using that once upstream fixed PowerPC host builds. If
IA64 doesn't use it (and I don't think they do), we can probably drop
that patch completely, which should make future merges a little
easier...
IA64 people?
--
Hollis Blanchard
IBM Linux Technology Center
next prev parent reply other threads:[~2008-12-03 19:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-02 15:37 powerpc kvm-userspace build fixes Hollis Blanchard
[not found] ` <1228232229-14360-1-git-send-email-hollisb-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2008-12-02 15:37 ` [PATCH 1/2] qemu: ppc: fix build after qemu upstream changes Hollis Blanchard
2008-12-02 15:37 ` [PATCH 2/2] qemu: ppc: fix build warnings Hollis Blanchard
2008-12-03 11:04 ` powerpc kvm-userspace build fixes Avi Kivity
2008-12-03 11:05 ` Avi Kivity
2008-12-03 19:03 ` Hollis Blanchard [this message]
2008-12-04 2:12 ` Zhang, Xiantao
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=1228331016.10084.30.camel@localhost.localdomain \
--to=hollisb@us.ibm.com \
--cc=avi@redhat.com \
--cc=kvm-ia64@vger.kernel.org \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox