[Bug 53539] maybe a --with-wine-64 build should call widl with -win32 option

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=53539

--- Comment #4 from j-r at online.de ---
(In reply to j-r from comment #3)
> (In reply to j-r from comment #2)
> > 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?
> 
> I mean without --with-wine-tools=, but even with --with-wine-tools= they may
> be defaulting to 64 bit. AFAICT the only thing the build cares about is that
> they can be executed on the build host.

Looking at the TARGETFLAGS section of configure.ac, it's not clear to me

 - why x86_32 build hosts are handled differently form x86_64 at all. Are there
supported toolchains for the wine32 build that don't support -m32/-m64?

 - why cross building enters into the consideration for x86_64 build hosts. At
least on Debian stable it seems that passing -m32 to the default X86_64 gcc is
not enough to build a 32 bit executable (because it cannot find a suitable
libgcc) and installing i686-linux-gnu-gcc is the easiest way out; while just
passing CC=i686-linux-gnu-gcc to configure is enough for the build to succeed,
technically it's a cross build and using --host=i686-linux-gnu doesn't seem
less correct and shouldn't be blocked

 - why the ms_va_list test build is done without -m64.

I'll try a few test builds with the above points changed and debian's gcc
packages.

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.