From: Mircea Gherzan <mircea.gherzan@intel.com>
To: tromey@redhat.com, palves@redhat.com, jan.kratochvil@redhat.com
Cc: gdb-patches@sourceware.org, Mircea Gherzan <mircea.gherzan@intel.com>
Subject: [PATCH 1/7] gdbserver, common: conditionally include the unistd.h
Date: Thu, 27 Jun 2013 08:44:00 -0000 [thread overview]
Message-ID: <1372322622-3216-2-git-send-email-mircea.gherzan@intel.com> (raw)
In-Reply-To: <1372322622-3216-1-git-send-email-mircea.gherzan@intel.com>
2013-06-25 Mircea Gherzan <mircea.gherzan@intel.com>
* common/agent.c: Conditionally include unistd.h.
gdbserver/
* hostio.c: Conditionally include unistd.h and define PATH_MAX
if unistd.h is not available.
* tracepoint.h: Conditionally include unistd.h.
Signed-off-by: Mircea Gherzan <mircea.gherzan@intel.com>
---
gdb/common/agent.c | 2 ++
gdb/gdbserver/hostio.c | 7 +++++++
gdb/gdbserver/tracepoint.c | 2 ++
3 files changed, 11 insertions(+)
diff --git a/gdb/common/agent.c b/gdb/common/agent.c
index 99cef4f..bbf5c4c 100644
--- a/gdb/common/agent.c
+++ b/gdb/common/agent.c
@@ -26,7 +26,9 @@
#endif
#include <string.h>
+#ifdef HAVE_UNISTD_H
#include <unistd.h>
+#endif
#include "agent.h"
#include "filestuff.h"
diff --git a/gdb/gdbserver/hostio.c b/gdb/gdbserver/hostio.c
index df94d31..3cf93db 100644
--- a/gdb/gdbserver/hostio.c
+++ b/gdb/gdbserver/hostio.c
@@ -23,7 +23,14 @@
#include <fcntl.h>
#include <limits.h>
+#ifdef HAVE_UNISTD_H
#include <unistd.h>
+#endif
+
+/* PATH_MAX is defined in unistd.h, which might not be available. */
+#ifndef PATH_MAX
+#define PATH_MAX 4096
+#endif
extern int remote_debug;
diff --git a/gdb/gdbserver/tracepoint.c b/gdb/gdbserver/tracepoint.c
index 5c0dec7..c0dea5b 100644
--- a/gdb/gdbserver/tracepoint.c
+++ b/gdb/gdbserver/tracepoint.c
@@ -22,7 +22,9 @@
#include <ctype.h>
#include <fcntl.h>
+#ifdef HAVE_UNISTD_H
#include <unistd.h>
+#endif
#include <sys/time.h>
#include <stddef.h>
#include <inttypes.h>
--
1.7.12.4
next prev parent reply other threads:[~2013-06-27 8:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-27 8:44 [PATCH 0/7] increase the portability of the gdbserver code Mircea Gherzan
2013-06-27 8:44 ` [PATCH 6/7] common: add an alternative implementation for xstrvprintf Mircea Gherzan
2013-07-29 19:16 ` Tom Tromey
2013-06-27 8:44 ` [PATCH 4/7] gdbserver: conditionally include sys/param.h and sys/time.h Mircea Gherzan
2013-06-28 16:34 ` Tom Tromey
2013-07-02 14:46 ` Mircea Gherzan
2013-06-27 8:44 ` [PATCH 3/7] gdbserver: avoid empty structs when not using GCC Mircea Gherzan
2013-06-28 16:04 ` Tom Tromey
2013-06-27 8:44 ` [PATCH 2/7] gdbserver, common: convert some variadic macros to C99 Mircea Gherzan
2013-06-28 16:02 ` Tom Tromey
2013-06-27 8:44 ` Mircea Gherzan [this message]
2013-06-27 13:29 ` [PATCH 1/7] gdbserver, common: conditionally include the unistd.h Pedro Alves
2013-06-27 19:19 ` Pedro Alves
2013-06-28 15:16 ` Mircea Gherzan
2013-06-28 18:26 ` Pedro Alves
2013-07-01 11:32 ` Pedro Alves
2013-06-27 8:45 ` [PATCH 7/7] gdbserver: add fallback implementation for memmem Mircea Gherzan
2013-06-27 19:27 ` Pedro Alves
2013-06-28 15:18 ` Mircea Gherzan
2013-06-27 11:32 ` [PATCH 5/7] gdbserver, win32: fix some function typedefs Mircea Gherzan
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=1372322622-3216-2-git-send-email-mircea.gherzan@intel.com \
--to=mircea.gherzan@intel.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=palves@redhat.com \
--cc=tromey@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