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

From	Chet Ramey <chet.ramey@case.edu>
Newsgroups	gnu.bash.bug
Subject	Re: [PATCH 1/3] aclocal.m4: Fix BASH_FUNC_STRSIGNAL when compiling for FreeBSD/RISC-V
Date	2020-06-29 10:42 -0400
Organization	ITS, Case Western Reserve University
Message-ID	<mailman.645.1593441772.2574.bug-bash@gnu.org> (permalink)
References	<20200627200631.38456-1-jrtc27@jrtc27.com> <20200627200631.38456-2-jrtc27@jrtc27.com> <21733b7d-0dbb-b74c-f508-ce16e12ae46f@case.edu>

Show all headers | View raw

On 6/27/20 4:06 PM, Jessica Clarke wrote:
> 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.

Thanks. This was fixed in the devel branch back last September as the
result of

https://lists.gnu.org/archive/html/bug-bash/2019-09/msg00016.html


-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
		 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU    chet@case.edu    http://tiswww.cwru.edu/~chet/

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

Thread

Re: [PATCH 1/3] aclocal.m4: Fix BASH_FUNC_STRSIGNAL when compiling for FreeBSD/RISC-V Chet Ramey <chet.ramey@case.edu> - 2020-06-29 10:42 -0400

csiph-web