[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: windows build failure

From: Paul Eggert
Subject: Re: windows build failure
Date: Sat, 12 Oct 2013 08:55:14 -0700
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0

Eli Zaretskii wrote:
> This is because MinGW32 runtime 4.0 also moved
> to using a 64-bit time_t type by default, which according to my
> testing screws up Emacs

What screwups do you observe?  Are they limited to MinGW32
or might they affect POSIXish 32-bit hosts with 64-bit time_t?

The reason I'm asking is that on on 32-bit hosts,
Emacs's hacky representation of time values is
limited to time_t values in the range [- 2**45, 2**45),
and Emacs reports an error via time_overflow when asked
to compute a time out of that range, even if it is operating
on a platform with 64-bit time_t values.  So, if you set your
system clock to 1116918-05-14 19:20:32 UTC on such a host,
or otherwise deal with outlandish time stamps, Emacs will
have screwups, and it won't be trivial to fix this.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]