qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Serge Hallyn <serge.hallyn@canonical.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: aliguori@us.ibm.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] virtio-9p-handle: define AT_EMPTY_PATH if needed
Date: Wed, 6 Jun 2012 13:02:50 -0500	[thread overview]
Message-ID: <20120606180250.GA10060@sergelap> (raw)
In-Reply-To: <877gvknxen.fsf@skywalker.in.ibm.com>

Quoting Aneesh Kumar K.V (aneesh.kumar@linux.vnet.ibm.com):
> Serge Hallyn <serge.hallyn@canonical.com> writes:
> 
> > If AT_EMPTY_PATH is not in one of the included files, go ahead and
> > define it.  qemu won't compile on ubuntu for me without this.
> >
> > (Note - alternatively we could #include <linux/fcntl.h> to pick
> > up the definitions there)
> 
> Then why don't we do that ? I do get the below errors
> 
> In file included from /usr/include/x86_64-linux-gnu/asm/fcntl.h:1:0,
>                  from /usr/include/linux/fcntl.h:4,
>                  from /home/opensource/sources/qemu/qemu-upstream/hw/9pfs/virtio-9p-handle.c:28:
> /usr/include/asm-generic/fcntl.h:127:8: error: redefinition of ‘struct f_owner_ex’
> /usr/include/x86_64-linux-gnu/bits/fcntl.h:204:8: note: originally defined here
> In file included from /usr/include/x86_64-linux-gnu/asm/fcntl.h:1:0,
>                  from /usr/include/linux/fcntl.h:4,
> 
> Are they do to ubuntu multi-arch changes ? 

I don't think so.  I got these awhile ago as well.  The libc and linux
headers simply don't seem to be compatible.

> >
> > Signed-off-by: Serge Hallyn <serge.hallyn@canonical.com>
> > ---
> >  hw/9pfs/virtio-9p-handle.c |    9 +++++++++
> >  1 files changed, 9 insertions(+), 0 deletions(-)
> >
> > diff --git a/hw/9pfs/virtio-9p-handle.c b/hw/9pfs/virtio-9p-handle.c
> > index f96d17a..e403a84 100644
> > --- a/hw/9pfs/virtio-9p-handle.c
> > +++ b/hw/9pfs/virtio-9p-handle.c
> > @@ -39,6 +39,15 @@
> >  #ifndef BTRFS_SUPER_MAGIC
> >  #define BTRFS_SUPER_MAGIC 0x9123683E
> >  #endif
> > +#ifndef AT_REMOVEDIR
> > +#define AT_REMOVEDIR    0x200
> > +#endif
> > +#ifndef AT_EMPTY_PATH
> > +#define AT_EMPTY_PATH   0x1000  /* Allow empty relative pathname */
> > +#endif
> > +#ifndef O_PATH
> > +#define O_PATH    010000000
> > +#endif
> >
> >  struct handle_data {
> >      int mountfd;
> > -- 
> > 1.7.9
> 
> -aneesh
> 

      reply	other threads:[~2012-06-06 18:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-24 19:51 [Qemu-devel] [PATCH] virtio-9p-handle: define AT_EMPTY_PATH if needed Serge Hallyn
2012-06-06 10:50 ` [Qemu-devel] [BUG QEMU 1.1] virtio-9p-handle does not compile Stefano Stabellini
2012-06-06 16:29   ` Stefan Weil
2012-06-06 17:49     ` Serge Hallyn
2012-06-06 21:16       ` Stefan Weil
2012-06-06 21:30         ` Serge Hallyn
2012-06-07  3:45     ` Aneesh Kumar K.V
2012-06-06 17:49 ` [Qemu-devel] [PATCH] virtio-9p-handle: define AT_EMPTY_PATH if needed Aneesh Kumar K.V
2012-06-06 18:02   ` Serge Hallyn [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=20120606180250.GA10060@sergelap \
    --to=serge.hallyn@canonical.com \
    --cc=aliguori@us.ibm.com \
    --cc=aneesh.kumar@linux.vnet.ibm.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).