A quick guess would be the problem is glibc upstream commit 13c51549e2077f2f3bf84e8fd0b46d8b0c615912, combined with upstream commit a26918cfda4bc4b9dad8aae1496e3ef7cbb63d96 setting __ASSUME_TIME64_SYSCALLS based on the *build* time kernel (not runtime kernel), and since our build farm runs a kernel older than 5.1, __ASSUME_TIME64_SYSCALLS remains unset for armhf. For all our other archs, __WORDSIZE == 64 I think, so only armhf would be affected.
Haven't looked very deep at what a proper fix would be though.
A quick guess would be the problem is glibc upstream commit 13c51549e2077f2 f3bf84e8fd0b46d 8b0c615912, combined with upstream commit a26918cfda4bc4b 9dad8aae1496e3e f7cbb63d96 setting __ASSUME_ TIME64_ SYSCALLS based on the *build* time kernel (not runtime kernel), and since our build farm runs a kernel older than 5.1, __ASSUME_ TIME64_ SYSCALLS remains unset for armhf. For all our other archs, __WORDSIZE == 64 I think, so only armhf would be affected.
Haven't looked very deep at what a proper fix would be though.