From: Anthony Liguori <anthony@codemonkey.ws>
To: Hollis Blanchard <hollis_blanchard@mentor.com>
Cc: mst@redhat.com, Arnd Bergmann <arnd@arndb.de>,
Gleb Natapov <gleb@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] vhost_net.c broken by --kerneldir
Date: Thu, 26 Aug 2010 14:01:13 -0500 [thread overview]
Message-ID: <4C76B9F9.2040808@codemonkey.ws> (raw)
In-Reply-To: <4C76992B.4030902@mentor.com>
On 08/26/2010 11:41 AM, Hollis Blanchard wrote:
> On 08/26/2010 08:48 AM, Anthony Liguori wrote:
>> On 08/26/2010 10:21 AM, Gleb Natapov wrote:
>>> You forgot about developers. Developer may want to use latest kvm
>>> kernel
>>> headers to compile code that he added to qemu to use new kernel
>>> feature.
>>
>> The Right Way to do this is a make headers_install to a temporary
>> directory and then -I include that directory. Building directly from
>> the kernel source tree was never the right thing to do.
>
> Thanks, this worked well.
>
> What are your thoughts on renaming the configure option to
> --kernel-headers?
>
> --kerneldir=PATH look for kernel includes in PATH
That's fine but FWIW, --kerneldir was intended to work with a kernel
source tree. It's just that that's become impossible in recent kernels.
Regards,
Anthon Liguori
> Hollis Blanchard
> Mentor Graphics, Embedded Systems Division
>
next prev parent reply other threads:[~2010-08-26 19:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-25 0:55 [Qemu-devel] vhost_net.c broken by --kerneldir Hollis Blanchard
2010-08-25 13:37 ` Arnd Bergmann
2010-08-25 17:22 ` Hollis Blanchard
2010-08-26 15:15 ` Arnd Bergmann
2010-08-26 15:21 ` Gleb Natapov
2010-08-26 15:48 ` Anthony Liguori
2010-08-26 16:41 ` Hollis Blanchard
2010-08-26 19:01 ` Anthony Liguori [this message]
2010-08-26 15:50 ` Arnd Bergmann
2010-09-03 10:57 ` Michael S. Tsirkin
2010-08-25 17:21 ` [Qemu-devel] " Hollis Blanchard
2010-08-26 6:29 ` Gleb Natapov
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=4C76B9F9.2040808@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=arnd@arndb.de \
--cc=gleb@redhat.com \
--cc=hollis_blanchard@mentor.com \
--cc=mst@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).