* [PATCH] Include endian.h when handling BYTE_ORDER
@ 2017-04-20 15:07 Ulf Hermann
2017-04-26 23:09 ` Mark Wielaard
0 siblings, 1 reply; 2+ messages in thread
From: Ulf Hermann @ 2017-04-20 15:07 UTC (permalink / raw)
To: elfutils-devel
BYTE_ORDER and friends are customarily defined in endian.h.
Signed-off-by: Ulf Hermann <ulf.hermann@qt.io>
---
libdw/ChangeLog | 4 ++++
libdw/dwarf_begin_elf.c | 1 +
2 files changed, 5 insertions(+)
diff --git a/libdw/ChangeLog b/libdw/ChangeLog
index c9ae664..8802853 100644
--- a/libdw/ChangeLog
+++ b/libdw/ChangeLog
@@ -1,5 +1,9 @@
2017-04-20 Ulf Hermann <ulf.hermann@qt.io>
+ * dwarf_begin_elf.c: Include endian.h.
+
+2017-04-20 Ulf Hermann <ulf.hermann@qt.io>
+
* libdw.h: Remove attribute macro declarations and use
__noreturn_attribute__ as defined in libelf.h.
diff --git a/libdw/dwarf_begin_elf.c b/libdw/dwarf_begin_elf.c
index 6f25e42..afa15ce 100644
--- a/libdw/dwarf_begin_elf.c
+++ b/libdw/dwarf_begin_elf.c
@@ -41,6 +41,7 @@
#include <sys/types.h>
#include <sys/stat.h>
#include <fcntl.h>
+#include <endian.h>
#include "libdwP.h"
--
2.1.4
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [PATCH] Include endian.h when handling BYTE_ORDER
2017-04-20 15:07 [PATCH] Include endian.h when handling BYTE_ORDER Ulf Hermann
@ 2017-04-26 23:09 ` Mark Wielaard
0 siblings, 0 replies; 2+ messages in thread
From: Mark Wielaard @ 2017-04-26 23:09 UTC (permalink / raw)
To: Ulf Hermann; +Cc: elfutils-devel
On Thu, 2017-04-20 at 17:07 +0200, Ulf Hermann wrote:
> BYTE_ORDER and friends are customarily defined in endian.h.
Right. Which we do in all other places where BYTE_ORDER is used.
Pushed to master.
Thanks,
Mark
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2017-04-26 15:20 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-04-20 15:07 [PATCH] Include endian.h when handling BYTE_ORDER Ulf Hermann
2017-04-26 23:09 ` Mark Wielaard
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 read-only IMAP folder(s) and NNTP newsgroup(s).