Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <yao@codesourcery.com>
To: <gdb-patches@sourceware.org>
Subject: [patch] Check readlink during configuring gdbserver
Date: Thu, 09 Feb 2012 02:45:00 -0000	[thread overview]
Message-ID: <4F33332D.4040207@codesourcery.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 584 bytes --]

I tried to build gdbserver as host=i686-mingw32 on linux, but get the
following error,

cc1: warnings being treated as errors
../gdb/gdb/gdbserver/hostio.c: In function 'handle_readlink':
../gdb/gdb/gdbserver/hostio.c:475: error: implicit declaration of
function 'readlink'

Even I remove -Werror temporarily, `readlink' can't be found during
linking,

hostio.o: In function `handle_readlink':
../gdb/gdb/gdbserver/hostio.c:475: undefined reference to `_readlink'

This patch is to add `readlink' in AC_CHECK_FUNCS, to check it
during configure.  OK to apply?

-- 
Yao (齐尧)

[-- Attachment #2: 0001-check-readlink.patch --]
[-- Type: text/x-patch, Size: 2475 bytes --]


gdb/gdbserver:
2012-02-08  Yao Qi  <yao@codesourcery.com>

	* configure.ac: Check for readlink.
	* configure, config.in: Regenerated.
	* hostio.c (handle_readlink) [!HAVE_READLINK]: Write error in packet.
---
 gdb/gdbserver/config.in    |    3 +++
 gdb/gdbserver/configure    |    2 +-
 gdb/gdbserver/configure.ac |    2 +-
 gdb/gdbserver/hostio.c     |    5 +++++
 4 files changed, 10 insertions(+), 2 deletions(-)

diff --git a/gdb/gdbserver/config.in b/gdb/gdbserver/config.in
index a9472ea..7fa3b5b 100644
--- a/gdb/gdbserver/config.in
+++ b/gdb/gdbserver/config.in
@@ -128,6 +128,9 @@
 /* Define to 1 if you have the `pwrite' function. */
 #undef HAVE_PWRITE
 
+/* Define to 1 if you have the `readlink' function. */
+#undef HAVE_READLINK
+
 /* Define to 1 if you have the <sgtty.h> header file. */
 #undef HAVE_SGTTY_H
 
diff --git a/gdb/gdbserver/configure b/gdb/gdbserver/configure
index d92a00f..e251844 100755
--- a/gdb/gdbserver/configure
+++ b/gdb/gdbserver/configure
@@ -4163,7 +4163,7 @@ fi
 
 done
 
-for ac_func in pread pwrite pread64
+for ac_func in pread pwrite pread64 readlink
 do :
   as_ac_var=`$as_echo "ac_cv_func_$ac_func" | $as_tr_sh`
 ac_fn_c_check_func "$LINENO" "$ac_func" "$as_ac_var"
diff --git a/gdb/gdbserver/configure.ac b/gdb/gdbserver/configure.ac
index 30666ec..7c86cd4 100644
--- a/gdb/gdbserver/configure.ac
+++ b/gdb/gdbserver/configure.ac
@@ -43,7 +43,7 @@ AC_CHECK_HEADERS(sgtty.h termio.h termios.h sys/reg.h string.h dnl
 		 errno.h fcntl.h signal.h sys/file.h malloc.h dnl
 		 sys/ioctl.h netinet/in.h sys/socket.h netdb.h dnl
 		 netinet/tcp.h arpa/inet.h sys/wait.h)
-AC_CHECK_FUNCS(pread pwrite pread64)
+AC_CHECK_FUNCS(pread pwrite pread64 readlink)
 AC_REPLACE_FUNCS(memmem vasprintf vsnprintf)
 
 # Check for UST
diff --git a/gdb/gdbserver/hostio.c b/gdb/gdbserver/hostio.c
index 34e4fa8..b1b104b 100644
--- a/gdb/gdbserver/hostio.c
+++ b/gdb/gdbserver/hostio.c
@@ -459,6 +459,8 @@ handle_unlink (char *own_buf)
 static void
 handle_readlink (char *own_buf, int *new_packet_len)
 {
+#if defined (HAVE_READLINK)
   char filename[PATH_MAX], linkname[PATH_MAX];
   char *p;
   int ret, bytes_sent;
@@ -485,6 +487,9 @@ handle_readlink (char *own_buf, int *new_packet_len)
      to return a partial response, but simply fail.  */
   if (bytes_sent < ret)
     sprintf (own_buf, "F-1,%x", FILEIO_ENAMETOOLONG);
+#else
+  hostio_packet_error (own_buf);
+#endif
 }
 
 /* Handle all the 'F' file transfer packets.  */
-- 
1.7.0.4


             reply	other threads:[~2012-02-09  2:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-09  2:45 Yao Qi [this message]
2012-02-09  2:53 ` Joel Brobecker
2012-02-09  3:02   ` Yao Qi

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=4F33332D.4040207@codesourcery.com \
    --to=yao@codesourcery.com \
    --cc=gdb-patches@sourceware.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