Re: [master b3cf281] Unbreak the MinGW build

[Eli Zaretskii <eliz@gnu.org>]

> From: Bruno Haible <bruno@clisp.org>
> Cc: bug-gnulib@gnu.org, Paul Eggert <eggert@cs.ucla.edu>, emacs-devel@gnu.org
> Date: Fri, 16 Dec 2016 19:11:31 +0100
> 
> On mingw, the fpending.o generated by this code, with or without this
> #include <errno.h>, is identical (even with debugging information [-g]).

Yes, I said that much.  Which is why this is a mystery in my eyes.

> I wouldn't have applied this patch, as the cause of the crash is obviously
> somewhere else.

I know.  I just don't know where, and have run out of ideas.
Suggestions welcome, but I cannot continue my work on Emacs without
being able to build the latest HEAD of the master branch.  Having
uncommitted/unpushed changes in master means I need to jump through
hoops each time I need to push a change upstream.

> - How often have you tried to temacs+dump with and without the change?
>   Once each? Twice each? 10 times each? If it's a small number, you may
>   be seeing a random result and not realize it was random.

I did it in two separate branches, 3 times in each one.  The results
are consistent.  This crash isn't random.

> - Did you run temacs in the same directory in both cases, or in different
>   directories? Different directories could lead to a different memory
>   layout in temacs, due to different filename lengths.

Same directory.

> - After determining that disabling the include would fix the crash, did
>   you test whether reenable the include would reenable the crash?

Yes.