https://bugzilla.suse.com/show_bug.cgi?id=1223169 https://bugzilla.suse.com/show_bug.cgi?id=1223169#c13 --- Comment #13 from Michael Matz <matz@suse.com> --- I guess you need to test for real in such a VM to be 100% sure. But yes, we aren't using 64bit time_t on 32bit and won't for a long time (if ever, considering that x86 might be done for good in 2038). Even Debian made an experiment about that only in 2023 with many issues, and glibc doesn't provide (yet) a default switch but requires compiling with -D_TIME_BITS=64 (and that changes the ABI everywhere! So don't use!). See e.g.: https://wiki.debian.org/ReleaseGoals/64bit-time And Bernhard: if your goal is to check for Y2038 compatibility, don't do that for -m32. We know it's not going to work, no sense in trying. -- You are receiving this mail because: You are on the CC list for the bug.