From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Sheng Yang <sheng.yang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [PATCH] KVM: Fix compile error caused by no defined CONFIG_X86
Date: Tue, 27 Nov 2007 10:38:12 +0200 [thread overview]
Message-ID: <474BD774.6090404@qumranet.com> (raw)
In-Reply-To: <200711271443.18291.sheng.yang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Sheng Yang wrote:
> From c050ed6225f314b86a0dabf11c7f677de097c39f Mon Sep 17 00:00:00 2001
> From: Sheng Yang <sheng.yang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
> Date: Tue, 27 Nov 2007 14:41:06 +0800
> Subject: [PATCH] KVM: Fix compile error caused by no defined CONFIG_X86
>
> For <linux/kvm.h> was included by qemu, which didn't define CONFIG_X86,
> kvm compiles fail on x86 machines.
>
> Using __i386__ and __x86_64__ instead.
>
>
For use as an exported header (installed in /usr/include) CONFIG_86 is
okay, since we run unifdef. For use in development, I added
-DCONFIG_X86 to the qemu flags for now.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
prev parent reply other threads:[~2007-11-27 8:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-27 6:43 [PATCH] KVM: Fix compile error caused by no defined CONFIG_X86 Sheng Yang
[not found] ` <200711271443.18291.sheng.yang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2007-11-27 8:38 ` Avi Kivity [this message]
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=474BD774.6090404@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=sheng.yang-ral2JQCrhuEAvxtiuMwx3w@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