From: Anthony Liguori <anthony@codemonkey.ws>
To: jyoung5@us.ibm.com
Cc: kvm-devel <kvm-devel@lists.sourceforge.net>,
hollisb <hollisb@linux.vnet.ibm.com>
Subject: Re: [RFC] Qemu powerpc work around
Date: Tue, 12 Feb 2008 16:03:44 -0600 [thread overview]
Message-ID: <47B217C0.5070905@codemonkey.ws> (raw)
In-Reply-To: <1202853180.16861.10.camel@thinkpad.austin.ibm.com>
Jerone Young wrote:
>> You can still generate a #define TARGET_PPCEMB too to keep other things
>> working.
>>
>
> I'll do this. But the issue here in upstream qemu this header is only
> defined under tcg/i386 & tcg/x86_64. So everyone else is out of luck.
>
>
>> Likewise, the same is true in the Makefile. You can't conditionally
>> link against TCG if it's x86_64, you need to conditionally link if it's
>> anything but PPCEMB_KVM.
>>
>
> The issue here is TCG is only for x86-64 & i386. No one else can use it.
> Is everyone else supposed to work then?
>
But your "solution" doesn't fix anyone else. It just causes a broken
build for them :-)
Regards,
Anthony Liguori
>> Regards,
>>
>> Anthony Liguori
>>
>>
>
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
next prev parent reply other threads:[~2008-02-12 22:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-12 21:37 [RFC] Qemu powerpc work around Jerone Young
2008-02-12 21:44 ` Anthony Liguori
2008-02-12 21:53 ` Jerone Young
2008-02-12 22:03 ` Anthony Liguori [this message]
2008-02-12 22:50 ` Jerone Young
2008-02-13 0:47 ` Anthony Liguori
2008-02-13 7:29 ` Avi Kivity
2008-02-13 17:39 ` Jerone Young
2008-02-13 18:55 ` Anthony Liguori
2008-02-13 19:27 ` [PATCH] " Jerone Young
2008-02-13 20:20 ` Anthony Liguori
2008-02-13 20:29 ` [RFC] " Jerone Young
2008-02-14 9:33 ` Avi Kivity
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=47B217C0.5070905@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=hollisb@linux.vnet.ibm.com \
--cc=jyoung5@us.ibm.com \
--cc=kvm-devel@lists.sourceforge.net \
/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