qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Weil <sw@weilnetz.de>
To: Serge Hallyn <serge.hallyn@canonical.com>
Cc: "aliguori@us.ibm.com" <aliguori@us.ibm.com>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	aneesh.kumar@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [BUG QEMU 1.1] virtio-9p-handle does not compile
Date: Wed, 06 Jun 2012 18:29:17 +0200	[thread overview]
Message-ID: <4FCF855D.8050208@weilnetz.de> (raw)
In-Reply-To: <alpine.DEB.2.02.1206061135350.6030@kaball.uk.xensource.com>

Am 06.06.2012 12:50, schrieb Stefano Stabellini:
> Hi Anthony,
> currently QEMU 1.1 doesn't compile virtfs correctly on Ubuntu:
>
> qemu/hw/9pfs/virtio-9p-handle.c: In function ‘handle_update_file_cred’:
> qemu/hw/9pfs/virtio-9p-handle.c:66:58: error: ‘AT_EMPTY_PATH’ undeclared (first use in this function)
> qemu/hw/9pfs/virtio-9p-handle.c:66:58: note: each undeclared identifier is reported only once for each function it appears in
> qemu/hw/9pfs/virtio-9p-handle.c: In function ‘handle_lstat’:
> qemu/hw/9pfs/virtio-9p-handle.c:87:34: error: ‘AT_EMPTY_PATH’ undeclared (first use in this function)
> qemu/hw/9pfs/virtio-9p-handle.c: In function ‘handle_symlink’:
> qemu/hw/9pfs/virtio-9p-handle.c:314:62: error: ‘AT_EMPTY_PATH’ undeclared (first use in this function)
> qemu/hw/9pfs/virtio-9p-handle.c: In function ‘handle_link’:
> qemu/hw/9pfs/virtio-9p-handle.c:337:45: error: ‘AT_EMPTY_PATH’ undeclared (first use in this function)
> qemu/hw/9pfs/virtio-9p-handle.c: In function ‘handle_chown’:
> qemu/hw/9pfs/virtio-9p-handle.c:373:58: error: ‘AT_EMPTY_PATH’ undeclared (first use in this function)
>
>
> a patch was sent on the 24th of Feb to fix the issue (also see below):
>
> http://marc.info/?l=qemu-devel&m=133011313912147
>
> Even though it is not particularly pretty, in the absence of better
> alternatives it should probably be applied.
>
> Cheers,
>
> Stefano
>
>
>
>
>
> On Fri, 24 Feb 2012, Serge Hallyn wrote:
>> 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)
>>
>> 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


The patch will fix the compiler error messages, but will the
resulting code work? Maybe it has runtime dependencies
(Linux kernel?) which should be checked at runtime.

Would an enhanced test in configure be a better solution?
It could disable VirtFS automatically if the definitions
are missing.

On Ubuntu Lenny, there is no definition for AT_EMPTY_PATH,
not even in linux/fcntl.h.

Regards,
Stefan W.

  reply	other threads:[~2012-06-06 16:30 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 [this message]
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

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=4FCF855D.8050208@weilnetz.de \
    --to=sw@weilnetz.de \
    --cc=aliguori@us.ibm.com \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=serge.hallyn@canonical.com \
    --cc=stefano.stabellini@eu.citrix.com \
    /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).