[Bug 17340] winebuild does not respect --host & --target configure parameters

[wine-bugs at winehq.org]

http://bugs.winehq.org/show_bug.cgi?id=17340


Hin-Tak Leung <htl10 at users.sourceforge.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |htl10 at users.sourceforge.net




--- Comment #16 from Hin-Tak Leung <htl10 at users.sourceforge.net>  2009-02-16 17:43:59 ---
Alexandre made a commit (4d135d9a71477baa9ffca530b2e3046c3e0a7a26) to undo some
of the damage from the "fix" in 1.1.15. Nevertheless, I like to point out to
the original poster that there is no need to keep a cross-compile toolchain
(i386-linux-xxxxx) for building 32bit apps on 64-bit fedora. (I use x86_64
fedora myself). Just passing -m32 to both the compiler (CFLAGS for c, CXXFLAGS
for c++ , FGLAGS for fortran) and the linker (LDFLAGS) would do. 

That has been the case for all multi-arch OSes since multi-arch CPU support was
available in the compiler. i.e. since x86_64 and ppc64 CPUs were available. I
do that quite regularly for wine, R, ghostscript, and occasionally something
else. There are distinct advantages e.g. for memory footprint, and the 32-bit
build tends to better tested and have fewer bugs, etc.

FWIW, on multi-arch (x86_64/x86) Solaris and (ppc/ppc64) Mac OS X, the default
behavior of the GCC suite is to generate 32-bit code, so the opposite - "-m64"
is needed if one wants to build 64-bit apps on Solaris and Mac OS X.


-- 
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
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.