Year 2038 problem

Corinna Vinschen
Wed Nov 18 10:44:00 GMT 2015

On Nov 18 07:47, R. Diez wrote:
> Hi all:
> 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...

> On another note, there seems to be no way for tzset to report any
> parsing errors. That means the user does not know if the time zone
> string was parsed correctly.

This is per the standards.  tzset() is and always was a void function
returning no errors.  You could try checking tzname, but it's no safe


Corinna Vinschen
Cygwin Maintainer
Red Hat
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <>

More information about the Newlib mailing list