Arch Linux User Repository

I cannot reproduce in a clean build from a container with or without wine, but I feel your patch doesnt hurt :)

I also get checking for build system executable suffix... configure: error: Cannot determine executable suffix

Please fix it by using CC_FOR_BUILD variable. Here is a patch
https://paste.ee/p/QQMAs

checking for build system executable suffix... configure: error: Cannot determine executable suffix

maybe its because of binfmt, or wine ?

I'm having this error with the latest version:

checking for build system executable suffix... configure: error: Cannot determine executable suffix

yes, sorry

Fails with same error. You need to also patch aclocal.m4 line 3936 to change (./conftest) to (./conftest$i) Credit to dreisner from #archlinux on freenode.

I think I fixed it.

This fix did not work for me. I'm still getting the error pingplug posted.

==> Starting build()...
~/.cache/aurman/mingw-w64-gmp/src/gmp-6.1.2/build-i686-w64-mingw32 ~/.cache/aurman/mingw-w64-gmp/src/gmp-6.1.2
checking build system type... x86_64-pc-linux-gnu
checking host system type... i686-w64-mingw32
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for i686-w64-mingw32-strip... i686-w64-mingw32-strip
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking ABI=32
checking compiler i686-w64-mingw32-gcc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions --param=ssp-buffer-size=4  ... yes
checking compiler i686-w64-mingw32-gcc -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions --param=ssp-buffer-size=4  has sizeof(long)==4... yes
checking for i686-w64-mingw32-gcc... i686-w64-mingw32-gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.exe
checking for suffix of executables... .exe
checking whether we are cross compiling... yes
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether i686-w64-mingw32-gcc accepts -g... yes
checking for i686-w64-mingw32-gcc option to accept ISO C89... none needed
checking whether i686-w64-mingw32-gcc understands -c and -o together... yes
checking for i686-w64-mingw32-gcc option to accept ISO C99... none needed
checking for i686-w64-mingw32-gcc option to accept ISO Standard C... (cached) none needed
checking how to run the C preprocessor... i686-w64-mingw32-gcc -E
checking build system compiler i686-w64-mingw32-gcc... yes
checking for build system preprocessor... i686-w64-mingw32-gcc -E
checking for build system executable suffix... configure: error: Cannot determine executable suffix
==> ERROR: A failure occurred in build().
    Aborting...

${_arch}-configure --build=${CHOST} \
    --target=${_target}
    --prefix=/usr \
    --enable-cxx \
    --enable-fat \

which deals with a warning about using --build --target but doesn't fix the error.