https://bugs.winehq.org/show_bug.cgi?id=53539
--- Comment #2 from j-r@online.de --- (In reply to Zeb Figura from comment #1)
We do pass -m32 to widl invocations for i386 platforms. How are you invoking configure? Can you attach config.log, and also the full makedep generated widl command rather than the silent rules?
Thanks for the hint! Looks like it adds -m32 if uname -m is x64_64. Mine wasn't in this case, because my userland is still mostly 32 bit - even though kernel and tool chain are 64 bit - and I run in the 32 bit personality by default (i only switched for the wine64 build, which works fine) as to not confuse anything, which I inadvertently just did here. Sorry, my fault, obviously.
(Actually my reason for using the linux32 personality was that it's a i686 build and the generated Makefile picks up entries for gcc, g++, ar, ranlib etc. and I was too lazy to override them individually with the appropriate i686 targeted version or make sure that they are irrelevant. My /usr/bin/gcc and friends select the appropriate variant at runtime, so that it still looks like a normal 32 bit userland when run with linux32 personality. I only have this one system and quite a lot of legacy crap on it:-)
I'm wondering if it would be the right thing to pass -m32 (or TARGETFLAGS?) independent of build host, since the --with-wine64=... provided tools will always default to -m64, I think?
Anyway, it's fine for me either way. Thanks again for the quick response!