qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@redhat.com>
To: Hollis Blanchard <hollis_blanchard@mentor.com>
Cc: qemu-devel@nongnu.org, mst@redhat.com
Subject: Re: [Qemu-devel] Re: vhost_net.c broken by --kerneldir
Date: Thu, 26 Aug 2010 09:29:28 +0300	[thread overview]
Message-ID: <20100826062928.GQ10499@redhat.com> (raw)
In-Reply-To: <4C75510E.3080500@mentor.com>

On Wed, Aug 25, 2010 at 10:21:18AM -0700, Hollis Blanchard wrote:
> On 08/24/2010 05:55 PM, Hollis Blanchard wrote:
> >
> >The problem seems to be that jump from
> >/usr/include/bits/sigcontext.h to asm/sigcontext.h inside
> ><kerneldir> rather than inside /usr/include. It seems like adding
> >-Ikerneldir/arch/foo/include will always be a problem, since it
> >will always be used to satisfy "#include <asm/bar.h>". Only files
> >built with KVM_CFLAGS would be affected, and I guess vhost_net.c
> >accidentally gets into a broken include path where the other
> >KVM_CFLAGS files doesn't.
> 
> Small correction: kvm.c doesn't build either (when I configure
> --disable-vhost-net).
> 
I just add --extra-cflags=-D__EXPORTED_HEADERS__ to ./configure

--
			Gleb.

      reply	other threads:[~2010-08-26  6:30 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
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 [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=20100826062928.GQ10499@redhat.com \
    --to=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).