Re: [Hamlib-developer] Year 2038 issues

[Nate B. <n0...@n0...>]

* On 2024 19 Jan 14:03 -0600, gm3zza via Hamlib-developer wrote:
> 
> 
> On 19 January 2024, at 18:53, van Wüllen <van...@Ch...> wrote:
> 
> >What is the problem? On my system (Mac OS), sizeof(time_t) is 8, that is,
> >time_t is a 64-bit integer.
> >I guess in 14 years there will be no system around with
> >time_t being 32 bit.
> 
> That complacency is the problem. 

Exactly.

It's not out of the realm of possibility that I'll still have some 32
bit hardware laying around 14 years from now.  I doubt any of it will be
used to run Hamlib and on the only system I use Hamlib on I've been
running 64 bit Linux for years but that doesn't necessarily mitigate the
issue as I understand it (not well).

> Is there a defined 64bit time type in C? Hamlib is C isn't it? 

I believe that glibc does have a 64 bit time_t, but my
(mis)understanding is that time_t is limited to 32 bits.  Perhaps this
link is helpful:

https://www.gnu.org/software/libc/manual/html_node/64_002dbit-time-symbol-handling.html

I am not sure what other C libraries are doing for mitigation.

73, Nate

-- 
"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."
Web: https://www.n0nb.us
Projects: https://github.com/N0NB
GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819