From: Thomas Huth <thuth@redhat.com>
To: Frans de Boer <frans@fransdb.nl>,
qemu-devel@nongnu.org, qemu-stable <qemu-stable@nongnu.org>
Subject: Re: [Qemu-devel] Problem compiling qemu-2.11.1
Date: Sun, 4 Mar 2018 19:21:09 +0100 [thread overview]
Message-ID: <bf227ff2-d45a-a279-568f-c60968a0aa09@redhat.com> (raw)
In-Reply-To: <96ce9600-c1e3-c3d6-5c3d-7d30cf799e04@fransdb.nl>
On 04.03.2018 12:15, Frans de Boer wrote:
> LS,
>
> I try to compile qemu and get the next error message:
>
> mnt/rhome/frans-tw/data/projects/linux/kernel/qemu/qemu-2.11.1/util/memfd.c:40:12:
> error: static declaration of ‘memfd_create’ follows non-static declaration
> static int memfd_create(const char *name, unsigned int flags)
> ^~~~~~~~~~~~
> In file included from /usr/include/bits/mman-linux.h:115:0,
> from /usr/include/bits/mman.h:45,
> from /usr/include/sys/mman.h:41,
> from
> /mnt/rhome/frans-tw/data/projects/linux/kernel/qemu/qemu-2.11.1/include/sysemu/os-posix.h:29,
>
> from
> /mnt/rhome/frans-tw/data/projects/linux/kernel/qemu/qemu-2.11.1/include/qemu/osdep.h:104,
>
> from
> /mnt/rhome/frans-tw/data/projects/linux/kernel/qemu/qemu-2.11.1/util/memfd.c:28:
>
> /usr/include/bits/mman-shared.h:46:5: note: previous declaration of
> ‘memfd_create’ was here
> int memfd_create (const char *__name, unsigned int __flags) __THROW;
>
> I use the newest Tumbleweed of openSuse with the gcc 7.3.0 compiler suite.
>
> Suggestions?
Not sure, but it sounds like you need this patch on top:
https://git.qemu.org/?p=qemu.git;a=commitdiff;h=75e5b70e6b5dcc4f2219992
HTH,
Thomas
next prev parent reply other threads:[~2018-03-04 18:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-04 11:15 [Qemu-devel] Problem compiling qemu-2.1.1 Frans de Boer
2018-03-04 18:21 ` Thomas Huth [this message]
2018-03-04 19:00 ` Peter Maydell
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=bf227ff2-d45a-a279-568f-c60968a0aa09@redhat.com \
--to=thuth@redhat.com \
--cc=frans@fransdb.nl \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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).