On Thu, Oct 09, 2014 at 09:22:19PM +0200, Johannes Schindelin wrote: > Hi, > > On Wed, 8 Oct 2014, Marat Radchenko wrote: > > > +CC_MACH := $(shell sh -c '$(CC) -dumpmachine 2>/dev/null || echo not') > > There is a rather huge problem with that. The latest mingw-w64 release, > 4.9.1, does not do what you expect here: while '.../mingw32/bin/gcc -m32 > -o 32.exe test.c' and '.../mingw32/bin/gcc -m64 -o 64.exe test.c' work > fine, producing i686 and x86_64 executables respectively, > '.../mingw32/bin/gcc -dumpmachine' prints i686-w64-mingw32 *always*, even > when specifying the -m64 option. > > So unfortunately, the test introduced by this patch (intended to figure > out whether the build targets i686, and skip a compiler and a linker > option otherwise) is incorrect. According to [1], it is by design. For now, I suggest using separate gcc binaries for 32/64, without messing with -m32. Of course we can fallback to `./configure` that will determine bitness by compiling something. [1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52096#c1 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html