From: Tobias Frost <tobi@coldtobi.de>
To: Emil Velikov <emil.l.velikov@gmail.com>,
ML dri-devel <dri-devel@lists.freedesktop.org>,
Gary Wong <gtw@gnu.org>
Cc: Tobias Frost <tobi@coldtobi.de>
Subject: [PATCH] On hurd other includes are required to compile.
Date: Sun, 24 Apr 2016 10:09:50 +0200 [thread overview]
Message-ID: <1461485390-15878-2-git-send-email-tobi@coldtobi.de> (raw)
In-Reply-To: <1461485390-15878-1-git-send-email-tobi@coldtobi.de>
As both BSD and Hurd needs also the typedefs, so making sure that they are
become declared when not compiling for linux.
---
include/drm/drm.h | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/include/drm/drm.h b/include/drm/drm.h
index b4ebaa9..e77146f 100644
--- a/include/drm/drm.h
+++ b/include/drm/drm.h
@@ -42,10 +42,14 @@
#include <asm/ioctl.h>
typedef unsigned int drm_handle_t;
+#elif defined(__GNU__) /* this is hurd */
+#include <stdint.h>
+#include <mach/i386/ioccom.h>
#else /* One of the BSDs */
-
#include <sys/ioccom.h>
#include <sys/types.h>
+#endif
+#if !defined(__linux__)
typedef int8_t __s8;
typedef uint8_t __u8;
typedef int16_t __s16;
--
2.8.1
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-04-24 8:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-21 5:30 libdrm: Patch to compile on hurd Tobias Frost
2016-04-21 12:33 ` Emil Velikov
2016-04-24 8:00 ` Tobias Frost
2016-04-24 7:57 ` [PATCH] Workaround for systems that does not have PATH_MAX, like hurd Tobias Frost
2016-04-24 20:03 ` Emil Velikov
2016-04-24 8:09 ` libdrm: Patch to compile on hurd -- includes in drm.h Tobias Frost
2016-04-24 8:09 ` Tobias Frost [this message]
2016-04-24 20:20 ` [PATCH] On hurd other includes are required to compile Emil Velikov
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=1461485390-15878-2-git-send-email-tobi@coldtobi.de \
--to=tobi@coldtobi.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=emil.l.velikov@gmail.com \
--cc=gtw@gnu.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).