gnupg 1.9.15 test fails on x86_64 and ppc
mschwendt at gmail.com
Fri May 13 15:18:57 CEST 2005
On 5/13/05, Werner Koch wrote:
> > I had added the following patch to 1.9.16 to get better output than
> > just "some signal":
> There are in fact two problems. The first is a change in the name of
> the test macro for sys_siglist
Yes, indeed. That also explains why it didn't use sys_siglist actually.
> and the second is that we did not print
> the signal number if sys_siglist is not available.
> > + const char* tmp = strsignal(signum);
> strsignal is a GNU extension, so at least a test would be needed.
> Further it is not reentrant, so we better avoid it.
> I have changed it in a better way by using onkly functions allowed
> within a signal handler. This will print all signal numbers in the
> range 0 .. 99999 which should be sufficient. On GNU systems
> sys_siglist is available and thus the code is only used on some other
Okay. Works here, and this is GNU. I just needed a quick way to get a
description of the received signal. The configure check for
sys_siglist was successful, but I think I only looked whether
HAVE_DECL_SYS_SIGLIST was true and then didn't look closer. ;)
More information about the Gnupg-devel