Year 2038 problem

Clemens Ladisch
Wed Nov 18 11:56:00 GMT 2015

Corinna Vinschen wrote:
> On Nov 18 07:47, R. Diez wrote:
>> I am developing embedded firmware on 32-bit ARM Cortex-Mx processors.
>> I believe that there is still no work-around for the year 2038 problem
>> in newlib, right?
> What kind of workaround are you looking for?  The usual one is to
> redefine time_t as 64 bit type...

Is changing _TIME_T_ to long long in newlib/libc/include/machine/types.h
and recompiling newlib something that is known to work?  Considering the
lack of a configuration option for this, I doubt that anybody ever tried.

Would such a simple configuration option be accepted into newlib?  (Most
embedded systems do not care about backwards compatibility, but newlib
as a whole probably does.)


More information about the Newlib mailing list