qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Ronald Delobel <rdelobel@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] make error
Date: Tue, 20 Feb 2018 16:40:49 +0100	[thread overview]
Message-ID: <CAMyPS3QVbV2FPNfE-Y_-kgpcpOTWr9zFWED50oCkJaBjJ3XtRg@mail.gmail.com> (raw)

Hello,

This is the error I get when building qemu-2.11.[0-1] with
gcc-7.3.0/glibc-2.27, removing the static attribute suffice to finnish the
build using the glibc provided memfd_create and qemu don't crash, but I
miss some knowledge here about what a static function really is, a kind of
private one? Shouldn't it be renamed instead and stay as static?

Just to report it.


  CC      util/qemu-thread-posix.o
  CC      util/memfd.o
util/memfd.c:40:12: error: la déclaration statique de « memfd_create » suit
une déclaration non statique
 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
/usr/local/src/qemu-2.11.1/include/sysemu/os-posix.h:29,
                 from /usr/local/src/qemu-2.11.1/include/qemu/osdep.h:104,
                 from util/memfd.c:28:
/usr/include/bits/mman-shared.h:46:5: note: la déclaration précédente de
« memfd_create » était ici
 int memfd_create (const char *__name, unsigned int __flags) __THROW;
     ^~~~~~~~~~~~
make: *** [/usr/local/src/qemu-2.11.1/rules.mak:66: util/memfd.o] Error 1

             reply	other threads:[~2018-02-20 15:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-20 15:40 Ronald Delobel [this message]
2018-03-06 11:31 ` [Qemu-devel] make error Stefan Hajnoczi

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=CAMyPS3QVbV2FPNfE-Y_-kgpcpOTWr9zFWED50oCkJaBjJ3XtRg@mail.gmail.com \
    --to=rdelobel@gmail.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).