[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH] Bad timestamps on MinGW32
From: |
Eli Zaretskii |
Subject: |
Re: [PATCH] Bad timestamps on MinGW32 |
Date: |
Thu, 03 Nov 2022 08:10:53 +0200 |
> From: Jeffrey Walton <noloader@gmail.com>
> Date: Wed, 2 Nov 2022 16:22:51 -0400
> Cc: bug-make@gnu.org
>
> You might also be interested in __MINGW64__.
That's possible, but AFAIK it is only defined after including some
headers; the compiler itself doesn't define it. Caveat emptor.
> I don't think it's a good idea to try to use MinGW or compiler
> versions as a proxy for 32- or 64-bit time_t. Things are in flux to
> fix the y2038 problem. The debian-arm and debian-powerpc lists are
> having discussions about it now. You will surely encounter 64-bit
> time_t on 32-bit machines eventually.
32-bit Windows have 64-bit time_t variant, but to use it you need to
redirect some function to non-default variants. 'stat' is on of those
functions.
> A first class configure test that checks for the size of time_t will
> probably be your best choice.
As I explained in my other mail, the issue here is not to know whether
the platform _can_ support 64-bit time data types, the issue is what
is the default, because libraries against Make is linked were most
probably compiled with that default.