Christopher Baines writes: > As it fails to build and seems broken. > > > Christopher Baines (2): > gnu: nss: Don't use libfaketime on 32bit systems. > gnu: python-pyopenssl: Don't use libfaketime on 32bit systems. > > gnu/packages/nss.scm | 15 +++++++++++++-- > gnu/packages/python-crypto.scm | 10 ++++++++-- > 2 files changed, 21 insertions(+), 4 deletions(-) libfaketime is actually good, it just fails the test because coreutils uses 64bit time_t. gnulib will enable 64bit time_t on 32bit platforms, but we don't currently support this, mixed abi will cause many problems[1], so turning off 64bit time_t on coreutils can fix libfaketime's tests, and nss can also use libfaketime because they use same time_t. And libfaketime is not provided 64-bit time_t support on 32-bit archs, see https://github.com/wolfcw/libfaketime/issues/418 We need to open a new branch to migrate time64 later And see also https://wiki.gentoo.org/wiki/Project:Toolchain/time64_migration https://wiki.debian.org/ReleaseGoals/64bit-time [1] https://bugs.gentoo.org/828001