public inbox for gdb-cvs@sourceware.org
help / color / mirror / Atom feed
From: Christian Biesinger <cbiesinger@sourceware.org>
To: gdb-cvs@sourceware.org
Subject: [binutils-gdb] Also check for strerror_r in gdbserver
Date: Thu, 31 Oct 2019 22:15:00 -0000	[thread overview]
Message-ID: <20191031221540.117261.qmail@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=e7e97a2ecd0e605d8128b3d055a8a5f7c2284b80

commit e7e97a2ecd0e605d8128b3d055a8a5f7c2284b80
Author: Christian Biesinger <cbiesinger@google.com>
Date:   Thu Oct 31 17:02:05 2019 -0500

    Also check for strerror_r in gdbserver
    
    I forgot to do this in b231e86ac9608056ea837e24d42a878927f5787a
    
    Since safe_strerror is in gdbsupport, gdbserver also needs to
    check for strerror_r, although it's less critical since gdbserver
    does not use threads as much.
    
    gdb/gdbserver/ChangeLog:
    
    2019-10-31  Christian Biesinger  <cbiesinger@google.com>
    
    	* config.in: Regenerate.
    	* configure: Regenerate.
    	* configure.ac: Also check for strerror_r.
    
    Change-Id: I6a67c8543cd7a28d6dc94f5986f56abcb55727fe

Diff:
---
 gdb/gdbserver/ChangeLog    | 6 ++++++
 gdb/gdbserver/config.in    | 3 +++
 gdb/gdbserver/configure    | 2 +-
 gdb/gdbserver/configure.ac | 2 +-
 4 files changed, 11 insertions(+), 2 deletions(-)

diff --git a/gdb/gdbserver/ChangeLog b/gdb/gdbserver/ChangeLog
index 9606596..ab03f88 100644
--- a/gdb/gdbserver/ChangeLog
+++ b/gdb/gdbserver/ChangeLog
@@ -1,5 +1,11 @@
 2019-10-31  Christian Biesinger  <cbiesinger@google.com>
 
+	* config.in: Regenerate.
+	* configure: Regenerate.
+	* configure.ac: Also check for strerror_r.
+
+2019-10-31  Christian Biesinger  <cbiesinger@google.com>
+
 	* ax.h (debug_agent): Remove duplicate declaration.
 
 2019-10-26  Tom de Vries  <tdevries@suse.de>
diff --git a/gdb/gdbserver/config.in b/gdb/gdbserver/config.in
index 0bce18d..2984281 100644
--- a/gdb/gdbserver/config.in
+++ b/gdb/gdbserver/config.in
@@ -229,6 +229,9 @@
 /* Define to 1 if you have the <stdlib.h> header file. */
 #undef HAVE_STDLIB_H
 
+/* Define to 1 if you have the `strerror_r' function. */
+#undef HAVE_STRERROR_R
+
 /* Define to 1 if you have the <strings.h> header file. */
 #undef HAVE_STRINGS_H
 
diff --git a/gdb/gdbserver/configure b/gdb/gdbserver/configure
index e513fc5..7bf9fa2 100755
--- a/gdb/gdbserver/configure
+++ b/gdb/gdbserver/configure
@@ -6448,7 +6448,7 @@ $as_echo "#define HAVE_WORKING_FORK 1" >>confdefs.h
 
 fi
 
-for ac_func in getauxval pread pwrite pread64 setns
+for ac_func in getauxval pread pwrite pread64 setns strerror_r
 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 7ebc9c3..44fee8b 100644
--- a/gdb/gdbserver/configure.ac
+++ b/gdb/gdbserver/configure.ac
@@ -90,7 +90,7 @@ AC_CHECK_HEADERS(termios.h sys/reg.h string.h dnl
 		 sys/ioctl.h netinet/in.h sys/socket.h netdb.h dnl
 		 netinet/tcp.h arpa/inet.h)
 AC_FUNC_FORK
-AC_CHECK_FUNCS(getauxval pread pwrite pread64 setns)
+AC_CHECK_FUNCS(getauxval pread pwrite pread64 setns strerror_r)
 
 GDB_AC_COMMON


                 reply	other threads:[~2019-10-31 22:15 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20191031221540.117261.qmail@sourceware.org \
    --to=cbiesinger@sourceware.org \
    --cc=gdb-cvs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).