@@ -28,9 +28,9 @@ Checking whether POSIX capabilities are available: OK
Checking if can we convert from CP850 to UCS-2LE: OK
Checking if can we convert from UTF-8 to UCS-2LE: OK
vfs_fileid checking for statfs() and struct statfs.f_fsid: OK
-Checking whether we can use Linux thread-specific credentials with 32-bit system calls: OK
+Checking whether we can use Linux thread-specific credentials: OK
Checking whether fcntl locking is available: OK
-Checking for the maximum value of the 'time_t' type: NO
+Checking for the maximum value of the 'time_t' type: OK
Checking whether the realpath function allows a NULL argument: OK
Checking for ftruncate extend: OK
getcwd takes a NULL argument: OK
The riscv32 cross answers were derived from arm, but riscv32 has no legacy 32-bit credential syscalls such as setresuid32, so samba asks "Checking whether we can use Linux thread-specific credentials" instead of the "with 32-bit system calls" variant. With no answer, configure fails: Checking whether we can use Linux thread-specific credentials : not found ... The configuration failed Answer it like riscv64 and aarch64 do. riscv32 also has a 64-bit time_t, so the time_t maximum value check succeeds like on 64-bit targets. Answer it OK so that samba does not limit TIME_T_MAX to INT32_MAX. Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com> --- .../files/waf-cross-answers/cross-answers-riscv32.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)