[PATCH 1/3] aclocal.m4: Fix BASH_FUNC_STRSIGNAL when compiling for FreeBSD/RISC-V

From	Jessica Clarke <jrtc27@jrtc27.com>
Newsgroups	gnu.bash.bug
Subject	[PATCH 1/3] aclocal.m4: Fix BASH_FUNC_STRSIGNAL when compiling for FreeBSD/RISC-V
Date	2020-06-27 21:06 +0100
Message-ID	<mailman.530.1593295309.2574.bug-bash@gnu.org> (permalink)
References	<20200627200631.38456-1-jrtc27@jrtc27.com> <20200627200631.38456-2-jrtc27@jrtc27.com>

Show all headers | View raw

POSIX defines strsignal(3) as being in string.h, not signal.h. We leave
the test as also checking signal.h for compatibility with any legacy
non-conforming systems.
---
 aclocal.m4 | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/aclocal.m4 b/aclocal.m4
index 1413267f..c4a54f27 100644
--- a/aclocal.m4
+++ b/aclocal.m4
@@ -300,7 +300,8 @@ AC_DEFUN(BASH_FUNC_STRSIGNAL,
 [AC_MSG_CHECKING([for the existence of strsignal])
 AC_CACHE_VAL(bash_cv_have_strsignal,
 [AC_TRY_LINK([#include <sys/types.h>
-#include <signal.h>],
+#include <signal.h>
+#include <string.h>],
 [char *s = (char *)strsignal(2);],
  bash_cv_have_strsignal=yes, bash_cv_have_strsignal=no)])
 AC_MSG_RESULT($bash_cv_have_strsignal)
-- 
2.20.1

Back to gnu.bash.bug | Previous | Next | Find similar

Thread

[PATCH 1/3] aclocal.m4: Fix BASH_FUNC_STRSIGNAL when compiling for FreeBSD/RISC-V Jessica Clarke <jrtc27@jrtc27.com> - 2020-06-27 21:06 +0100

csiph-web