All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Andi Kleen <andi@firstfloor.org>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Set a useful default for kerneldir
Date: Wed, 01 Jul 2009 18:10:11 +0300	[thread overview]
Message-ID: <4A4B7C53.4030306@redhat.com> (raw)
In-Reply-To: <4A4B653B.5010203@codemonkey.ws>

On 07/01/2009 04:31 PM, Anthony Liguori wrote:
> Andi Kleen wrote:
>> When no explicit kerneldir is specified use the standard
>> /lib/modules/$(uname -r)/build
>> convention to find the kernel includes. This should work out of the 
>> box on a large number of distributions.
>>
>> Also support separate objdirs.
>>
>> Signed-off-by: Andi Kleen <ak@linux.intel.com>
>
> The reason we don't specify an explicit include is that it makes it 
> possible to have a cross compiler with headers installed in the cross 
> compilers root.  If you default to /lib/modules, you have to 
> explicitly override it when cross compiling.
>
> Another option would be to just include the KVM headers in QEMU.

Or to have kvm-kmod install the headers in /usr/local/include.  I'm wary 
about that though, it makes qemu features depend on the installation 
order of qemu and kvm-kmod.

-- 
error compiling committee.c: too many arguments to function

  parent reply	other threads:[~2009-07-01 15:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-01  9:33 [Qemu-devel] [PATCH] Set a useful default for kerneldir Andi Kleen
2009-07-01 13:31 ` Anthony Liguori
2009-07-01 13:40   ` Andi Kleen
2009-07-01 15:10   ` Avi Kivity [this message]
2009-07-09 19:00 ` Anthony Liguori

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=4A4B7C53.4030306@redhat.com \
    --to=avi@redhat.com \
    --cc=andi@firstfloor.org \
    --cc=anthony@codemonkey.ws \
    --cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.