Re: [Hamlib-developer] Year 2038 issues

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

* On 2024 21 Jan 08:51 -0600, Greg Troxel wrote:
> Nate Bargmann <n0...@n0...> writes:
> 
> > 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).
> 
> This is not about systems with CPUs with 32-bit native word sizes.  It
> is about operating systems that choose a 32-bit type for time_t.

Apparently there are still places in the GNU/Linux world where that is
the case.  Linux Weekly News has been covering this for years:

https://lwn.net/Articles/776435/
https://lwn.net/Articles/812767/
https://lwn.net/Articles/938149/

and many more simply by searching for 2038 in the site's Search page.

I'm not going to debate who is right and who is not.  My effort is to
simply be sure that nothing is hiding in the Hamlib code that someone
comes along at some later date grumpily pointing out that this project
did not do its due diligence.

That is all.

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