Re: Windows port binaries

[Eli Zaretskii]

> From: Bruno Haible <bruno@clisp.org>
> Cc: Po Lu <luangruo@yahoo.com>, Paul Eggert <eggert@cs.ucla.edu>
> Date: Tue, 15 Aug 2023 21:57:47 +0200
> 
> >   https://corwin.bru.st/emacs-29
> >   https://corwin.bru.st/emacs-30
> 
> Thanks. I tried to use the
> https://corwin.bru.st/emacs-30/emacs-30-latest-no-deps.zip
> binary from today, but they don't work for me (on Windows 10), because
> they rely on two DLLs which are not contained in the 'bin' directory:
>   - libgmp-10.dll
>   - libwinpthread-1.dll

libwinpthread-1.dll shouldn't be there.  But maybe there's no way to
avoid that with MinGW64 ports of GCC.  See below.

> Find below the output of "dumpbin.exe /imports emacs.exe".

A more GNU-friendly way is

  objdump -p emacs.exe | fgrep "DLL Name:"

> Additionally, I find it strange:
> 
>   1) Why are the imports from libgmp all prefixed with '__'? That's
>      a bit unusual.

Why are you asking us?  The Emacs project doesn't build libgmp, it
only uses it.  This question shouldf go to the GMP developers, IMO.

>   2) emacs/nt/mingw-cfg.site contains this comment:
>        # We don't want to check for these functions
>        # because they are implemented in libwinpthread.
>      corresponding to this ChangeLog entry:
> 
>        2016-04-21  Fabrice Popineau  <fabrice.popineau@gmail.com>
> 
>                Avoid run-time dependency on libwinpthread DLL on MS-Windows
> 
>                * nt/mingw-cfg.site (ac_cv_search_clock_gettime)
>                (ac_cv_func_clock_gettime, ac_cv_func_clock_settime): Force to 
> not
>                present, so that MinGW64 builds don't depend on libwinpthread.
>                (Bug#22959)
> 
>      However, the binaries rely on nanosleep() from libwinpthread.
>      Is it intended or unintended?

I guess this is some kind of regression.  But I'm not sure we can
avoid this, when MinGW64 is used.  (I use mingw.org's MinGW, and my
Emacs on Windows doesn't have the libwinpthread dependency.)