Unfortunately this requested change has introduced severe issues with the kernels in which it was applied, by breaking compatibility with the 32bit glibc.
Even if an application is built with _TIME_BITS=64, and therefore the application has no year 2038 issues, glibc itself will use the 32bit time syscalls when there is no deadline or when the deadline fits in the 32bit syscall. See, apart from the issue linked above, these which provide more details: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2071445 https://github.com/actions/runner-images/issues/9977 Please note that it is quite normal to build and run 32bit applications in 64bit systems, and that it is the base for a lot of CI/test setups. ** Bug watch added: github.com/actions/runner-images/issues #9977 https://github.com/actions/runner-images/issues/9977 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2038582 Title: Turning COMPAT_32BIT_TIME off on arm64 (64k & derivatives) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038582/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
