bug#19111: 25.0.50; 32 bits temacs.exe is linked with wrong image-base when built on 64 bit Windows host

["Óscar Fuentes" <ofv@wanadoo.es>]

Eli Zaretskii <eliz@gnu.org> writes:

>> Since we already special-case MinGW on the configure script, and fixing
>> the problem there only changes how the special case is implemented
>> without touching new areas, I'll very much prefer to apply the patch
>> shown on my previous message and keep the nice and simple "configure &&
>> make" procedure working on all cases.
>
> OK, but at least let's keep the build/host/target triplet correct.
> It's not right for us to disregard it when it doesn't fit our needs,
> because the entire configure script is based on the notion that the
> triplet is the starting point on which all the rest is based.
>
> So, if we want to fix that, let's fix the triplet early on, to specify
> a i686 build, and let the rest of the script do its job as usual.

I suspect that you have a point here which I don't entirely grasp.

Are you thinking on a scenario where the user sets --host/--build on the
configure script to something that doesn't correlate to the contents of
$MSYSTEM?

> Besides, I came to a conclusion that I don't understand how your
> suggestion will work anyway.  AFAICT, you just replace tests based on
> one wrong string (x86_64-*-*) with another wrong string (MINGW64).
>
> Or are you saying that MSYS2 somehow magically does not give $MSYSTEM
> the value MINGW64 when you configure for a 32-bit build?  If so, how
> does this magic work?  Because if MSYS2 always sets MSYSTEM=MINGW64,
> then your suggestion isn't going to work, is it?
>
> More generally, how do you tell configure that you want a 32-bit build
> using MinGW64 toolchain?  That requires some special compiler switches
> (like -m32 or some such), no?

We are using $MSYSTEM to special-case MinGW(-w64). $MSYSTEM is MINGW32
when using the 32 bit toolset and MINGW64 when using the 64 bit toolset.
That's true for MSYS2/MinGW-w64. I'm not sure if MSYS sets $MSYSTEM to
MINGW or MINGW32, but any of it should be ok with the patch.

The -m32 switch is actively discouraged by the MinGW-w64 community and
the official builds does not support it.

Does this answer your questions?