Also check for strerror_r in gdbserver
authorChristian Biesinger <cbiesinger@google.com>
Thu, 31 Oct 2019 22:02:05 +0000 (17:02 -0500)
committerChristian Biesinger <cbiesinger@google.com>
Thu, 31 Oct 2019 22:14:54 +0000 (17:14 -0500)
commite7e97a2ecd0e605d8128b3d055a8a5f7c2284b80
tree0e7d3c3e780d3e0843f5ae2a98a594d74d37f622
parentd1e36019c1f5cc5de8b99dd86cacfbf418fc1c5b
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
gdb/gdbserver/ChangeLog
gdb/gdbserver/config.in
gdb/gdbserver/configure
gdb/gdbserver/configure.ac