On Tue, Apr 16, 2024 at 12:25:53AM +0200, Vincent Blut wrote: > I have yet to set up an armhf based environment to properly debug those > failures, > but the most likely cause seems to be the ongoing migration of our > 32-bits architectures to 64-bits time_t. If so, do you have an idea > about where the problem lies?
> ยน https://ci.debian.net/packages/c/chrony/unstable/armhf/45199616/#S6 The log shows that clknetsim is not built with the -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 flags. It needs to use the same time_t as the chronyd binaries. -- Miroslav Lichvar -- To unsubscribe email chrony-dev-requ...@chrony.tuxfamily.org with "unsubscribe" in the subject. For help email chrony-dev-requ...@chrony.tuxfamily.org with "help" in the subject. Trouble? Email listmas...@chrony.tuxfamily.org.
