Re: [Hamlib-developer] Issue with latest pull and building WSJT-X 2.7.0 [ clock_gettime64 could not be located in the DLL ]

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

* On 2025 19 May 10:17 -0500, George Baltz wrote:
> I noticed 'Build_OS is mingw32' yet something is looking for a 64 bit
> routine. Is that OK?

When I do a DDG for clock_gettime64 the first hit is:

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

I wonder if this is some sort of macro that MSYS2 is looking for?  Or,
that MinGW supplies from the C library.

Using objdump on an older 64 bit DLL I get:

$ objdump -p libhamlib-4.dll | grep clock_gettime
	bae924	   13  clock_gettime

And on today's 32 bit DLL:

$ objdump -p libhamlib-4.dll | grep clock_gettime
	a6823c	   13  clock_gettime

Searching for clock_gettime64 in either file returned zero results each.

Undoubtedly this has to do with Y2038 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