Source: samhain Version: 4.1.4-4 Severity: serious Tags: ftbfs X-Debbugs-CC: j...@debian.org
samhain previously built on s390x but now ftbfs there: https://buildd.debian.org/status/logs.php?suite=sid&arch=s390x&pkg=samhain&ver=4.1.4-4 https://buildd.debian.org/status/fetch.php?pkg=samhain&arch=s390x&ver=4.1.4-4&stamp=1735048699&raw=0 ... ./encode 0 ./src/sh_checksum.c --> x_sh_checksum.c s390x-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I./include -DUSE_MALLOC_LOCK=1 -Wl,-z,relro -fstack-protector-strong -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -fstack-protector-strong -DUSE_MALLOC_LOCK=1 -fPIE -Wall -W -fno-strength-reduce -fno-omit-frame-pointer -Wno-empty-body -DSH_STANDALONE -o sh_checksum.o -c x_sh_checksum.c x_sh_checksum.c:410:29: warning: argument 1 of type ‘sha2_byte[]’ {aka ‘unsigned char[]’} with mismatched bound [-Warray-parameter=] 410 | void SHA256_Final(sha2_byte digest[], SHA256_CTX* context) | ~~~~~~~~~~^~~~~~~~ In file included from x_sh_checksum.c:22: ./include/sh_checksum.h:22:19: note: previously declared as ‘sha2_byte[32]’ {aka ‘unsigned char[32]’} 22 | void SHA256_Final(sha2_byte[SHA256_DIGEST_LENGTH], SHA256_CTX*); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ x_sh_checksum.c: In function ‘SHA256_Final’: x_sh_checksum.c:471:22: error: passing argument 2 of ‘sl_memset’ makes integer from pointer without a cast [-Wint-conversion] 471 | memset(d, context->state, SHA256_DIGEST_LENGTH); | ~~~~~~~^~~~~~~ | | | sha2_word32 * {aka unsigned int *} In file included from /usr/include/features.h:510, from /usr/include/s390x-linux-gnu/sys/types.h:25, from ./include/samhain.h:23, from x_sh_checksum.c:21: /usr/include/s390x-linux-gnu/bits/string_fortified.h:57:1: note: expected ‘int’ but argument is of type ‘sha2_word32 *’ {aka ‘unsigned int *’} ... Would be nice if samhain wouldn't have its own copy of a sha256 implementation, possibly a buggy one.
