On Tue, Dec 11, 2018 at 11:29:14AM +0100, John Paul Adrian Glaubitz wrote: > I can't say anything about the syscall interface. However, what I do know > is that the weird combination of a 32-bit userland with a 64-bit kernel > interface is sometimes causing issues. For example, application code usually > expects things like time_t to be 32-bit on a 32-bit system. However, this > isn't the case for x32 which is why code fails to build. I don't see any basis for this claim about expecting time_t to be 32-bit. I've encountered some programs that "implicitly assume" this by virtue of assuming they can cast time_t to long to print it, or similar. IIRC this was an issue in busybox at one point; I'm not sure if it's been fixed. But any software that runs on non-Linux unices has long been corrected. If not, 2038 is sufficiently close that catching and correcting any such remaining bugs is more useful than covering them up and making the broken code work as expected. Rich
