From: Christopher Covington <cov@codeaurora.org>
To: qemu-devel@nongnu.org
Cc: "Eric Blake" <eblake@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@gmail.com>,
"Radim Krčmář" <rkrcmar@redhat.com>,
"Christopher Covington" <cov@codeaurora.org>
Subject: [Qemu-devel] [PATCH v2] build: include sys/sysmacros.h for major() and minor()
Date: Wed, 28 Dec 2016 09:53:44 -0500 [thread overview]
Message-ID: <20161228145344.30819-1-cov@codeaurora.org> (raw)
In-Reply-To: <CAJ+F1CJXGAZa5_+4jD0rP_zX28RCCu3xmF27ZHpgvhnZz686ug@mail.gmail.com>
The definition of the major() and minor() macros are moving within glibc to
<sys/sysmacros.h>. Include this header to avoid the following sorts of
build-stopping messages:
qga/commands-posix.c: In function ‘dev_major_minor’:
qga/commands-posix.c:656:13: error: In the GNU C Library, "major" is defined
by <sys/sysmacros.h>. For historical compatibility, it is
currently defined by <sys/types.h> as well, but we plan to
remove this soon. To use "major", include <sys/sysmacros.h>
directly. If you did not intend to use a system-defined macro
"major", you should undefine it after including <sys/types.h>. [-Werror]
*devmajor = major(st.st_rdev);
^~~~~~~~~~~~~~~~~~~~~~~~~~
qga/commands-posix.c:657:13: error: In the GNU C Library, "minor" is defined
by <sys/sysmacros.h>. For historical compatibility, it is
currently defined by <sys/types.h> as well, but we plan to
remove this soon. To use "minor", include <sys/sysmacros.h>
directly. If you did not intend to use a system-defined macro
"minor", you should undefine it after including <sys/types.h>. [-Werror]
*devminor = minor(st.st_rdev);
^~~~~~~~~~~~~~~~~~~~~~~~~~
The additional include allows the build to complete on Fedora 26 (Rawhide)
with glibc version 2.24.90.
Signed-off-by: Christopher Covington <cov@codeaurora.org>
---
include/sysemu/os-posix.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/sysemu/os-posix.h b/include/sysemu/os-posix.h
index b0a6c0695b..772d58f7ed 100644
--- a/include/sysemu/os-posix.h
+++ b/include/sysemu/os-posix.h
@@ -28,6 +28,7 @@
#include <sys/mman.h>
#include <sys/socket.h>
+#include <sys/sysmacros.h>
#include <netinet/in.h>
#include <netinet/tcp.h>
#include <arpa/inet.h>
--
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm
Technologies, Inc. Qualcomm Technologies, Inc. is a member of the Code Aurora
Forum, a Linux Foundation Collaborative Project.
next prev parent reply other threads:[~2016-12-28 14:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-22 20:56 [Qemu-devel] [PATCH] build: handle deprecation of major() in sys/types.h Radim Krčmář
2016-09-22 21:09 ` Marc-André Lureau
2016-12-28 14:53 ` Christopher Covington [this message]
2016-12-28 16:10 ` [Qemu-devel] [PATCH v2] build: include sys/sysmacros.h for major() and minor() Eric Blake
2016-12-28 17:07 ` Peter Maydell
2016-12-29 13:48 ` Eric Blake
2016-12-30 11:35 ` Peter Maydell
2016-12-28 20:03 ` Christopher Covington
2016-12-28 20:04 ` [Qemu-devel] [PATCH v3] " Christopher Covington
2016-12-29 14:03 ` Eric Blake
2017-03-13 18:31 ` Eric Blake
2017-03-14 10:12 ` Peter Maydell
2016-09-22 21:09 ` [Qemu-devel] [PATCH] build: handle deprecation of major() in sys/types.h Eric Blake
2016-09-22 21:10 ` no-reply
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=20161228145344.30819-1-cov@codeaurora.org \
--to=cov@codeaurora.org \
--cc=eblake@redhat.com \
--cc=marcandre.lureau@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=rkrcmar@redhat.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).