From: Anthony Liguori <anthony-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
To: "Dâniel Fraga" <fragabr-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [RFC] QEMU KVM target -> Anthony
Date: Sun, 18 Mar 2007 14:51:47 -0500 [thread overview]
Message-ID: <45FD9853.6040907@codemonkey.ws> (raw)
In-Reply-To: <daa0d4-m5d.ln1-wHoKvyfhNRggb5+hjvvj3w@public.gmane.org>
Dâniel Fraga wrote:
> On Sun, 18 Mar 2007 11:44:36 -0500
> Anthony Liguori <anthony-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org> wrote:
>
>
>> I'm not entirely sure it's the right thing to do. The proper
>> solution is qops.
>>
>> I also don't think it's a good idea to merge things into KVM that
>> wouldn't be reasonable to integrate into upstream QEMU. I think this
>> is probably the case with this one.
>>
>
> Ok, so for someone who wants to compile qemu with gcc4, what's
> the solution?
You really should use gcc3. You'll have a much better user experience
and honestly it's more useful to have the ability to run -no-kvm to
troubleshoot.
Is there a particular reason why gcc3 isn't available to you?
Regards,
Anthony Liguori
> I tried your patch, but it isn't applied correctly. Do
> you have an updated version of the patch?
>
> Thank you.
>
>
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
next prev parent reply other threads:[~2007-03-18 19:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-18 15:08 [RFC] QEMU KVM target -> Anthony Dâniel Fraga
[not found] ` <3810d4-k6b.ln1-wHoKvyfhNRggb5+hjvvj3w@public.gmane.org>
2007-03-18 16:44 ` Anthony Liguori
2007-03-18 17:43 ` Dâniel Fraga
[not found] ` <daa0d4-m5d.ln1-wHoKvyfhNRggb5+hjvvj3w@public.gmane.org>
2007-03-18 19:51 ` Anthony Liguori [this message]
2007-03-18 20:53 ` Dâniel Fraga
[not found] ` <3gl0d4-38g.ln1-wHoKvyfhNRggb5+hjvvj3w@public.gmane.org>
2007-03-18 22:36 ` Jim Paris
2007-03-18 23:23 ` Dâniel Fraga
2007-03-18 23:08 ` Ed Swierk
2007-03-19 0:08 ` Dâniel Fraga
[not found] ` <7t01d4-o0j.ln1-wHoKvyfhNRggb5+hjvvj3w@public.gmane.org>
2007-03-19 1:39 ` Anthony Liguori
2007-03-19 2:01 ` Dâniel Fraga
-- strict thread matches above, loose matches on Subject: below --
2007-03-18 22:42 Gregory Haskins
2007-03-18 22:50 ` Dâniel Fraga
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=45FD9853.6040907@codemonkey.ws \
--to=anthony-rdkfgonbjusknkdkm+me6a@public.gmane.org \
--cc=fragabr-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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