From: "Daniel P. Berrange" <berrange@redhat.com>
To: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] git master build failure in 9pfs
Date: Thu, 2 Mar 2017 17:40:26 +0000 [thread overview]
Message-ID: <20170302174026.GI11445@redhat.com> (raw)
In-Reply-To: <a8300848-9e60-7d62-d8bd-c0084691abbb@ilande.co.uk>
On Thu, Mar 02, 2017 at 05:28:24PM +0000, Mark Cave-Ayland wrote:
> Does anyone else see the following error when trying to build git master?
>
> cc -I/home/build/src/qemu/git/qemu/hw/9pfs -Ihw/9pfs
> -I/home/build/src/qemu/git/qemu/tcg
> -I/home/build/src/qemu/git/qemu/tcg/i386
> -I/home/build/src/qemu/git/qemu/linux-headers
> -I/home/build/src/qemu/git/qemu/linux-headers -I.
> -I/home/build/src/qemu/git/qemu -I/home/build/src/qemu/git/qemu/include
> -I/usr/include/pixman-1 -I/home/build/src/qemu/git/qemu/dtc/libfdt
> -Werror -pthread -I/usr/include/glib-2.0
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -m64 -mcx16 -D_GNU_SOURCE
> -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wstrict-prototypes
> -Wredundant-decls -Wall -Wundef -Wwrite-strings -Wmissing-prototypes
> -fno-strict-aliasing -fno-common -fwrapv -Wendif-labels
> -Wno-missing-include-dirs -Wempty-body -Wnested-externs
> -Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers
> -Wold-style-declaration -Wold-style-definition -Wtype-limits
> -fstack-protector-all -I/usr/include/p11-kit-1
> -I/usr/include/libpng12 -I/home/build/src/qemu/git/qemu/tests -MMD -MP
> -MT hw/9pfs/9p-util.o -MF hw/9pfs/9p-util.d -O2 -U_FORTIFY_SOURCE
> -D_FORTIFY_SOURCE=2 -g -c -o hw/9pfs/9p-util.o hw/9pfs/9p-util.c
> In file included from hw/9pfs/9p-util.c:15:0:
> hw/9pfs/9p-util.h: In function ‘openat_dir’:
> hw/9pfs/9p-util.h:25:57: error: ‘O_PATH’ undeclared (first use in this
> function)
> hw/9pfs/9p-util.h:25:57: note: each undeclared identifier is reported
> only once for each function it appears in
> hw/9pfs/9p-util.h:26:1: error: control reaches end of non-void function
> [-Werror=return-type]
>
> Build platform is Debian Wheezy on an x86_64 host.
IIUC, O_PATH was introduced in glibc 2.14 and Wheezy only has 2.13.
So unless we want to make this 9pfs code a configurable option, this
means Debian Wheezy is no longer a supportable platform for QEMU.
Regards,
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://entangle-photo.org -o- http://search.cpan.org/~danberr/ :|
next prev parent reply other threads:[~2017-03-02 17:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-02 17:28 [Qemu-devel] git master build failure in 9pfs Mark Cave-Ayland
2017-03-02 17:40 ` Daniel P. Berrange [this message]
2017-03-02 18:10 ` Peter Maydell
2017-03-03 15:41 ` Greg Kurz
2017-03-03 14:43 ` Mark Cave-Ayland
[not found] <mailman.56353.1488479169.22739.qemu-devel@nongnu.org>
2017-03-03 0:30 ` Programmingkid
[not found] <mailman.56273.1488553194.22740.qemu-devel@nongnu.org>
2017-03-03 15:28 ` G 3
2017-03-03 15:44 ` Greg Kurz
2017-03-03 15:55 ` G 3
2017-03-03 15:58 ` Peter Maydell
2017-03-03 16:02 ` G 3
2017-03-03 16:14 ` Greg Kurz
2017-03-03 16:21 ` Daniel P. Berrange
2017-03-03 16:38 ` G 3
2017-03-03 16:40 ` Eric Blake
2017-03-03 16:42 ` Daniel P. Berrange
2017-03-03 16:45 ` Eric Blake
2017-03-03 16:43 ` Greg Kurz
2017-03-03 18:11 ` Eric Blake
2017-03-03 18:15 ` Greg Kurz
2017-03-03 18:28 ` Eric Blake
2017-03-04 10:57 ` Greg Kurz
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=20170302174026.GI11445@redhat.com \
--to=berrange@redhat.com \
--cc=mark.cave-ayland@ilande.co.uk \
--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.