Package Details: mingw-w64-gmp 6.3.0-1

Git Clone URL: https://aur.archlinux.org/mingw-w64-gmp.git (read-only, click to copy)
Package Base: mingw-w64-gmp
Description: A free library for arbitrary precision arithmetic (mingw-w64)
Upstream URL: http://gmplib.org
Licenses: LGPL3
Submitter: Schala
Maintainer: xantares
Last Packager: xantares
Votes: 14
Popularity: 0.000000
First Submitted: 2012-08-08 04:25 (UTC)
Last Updated: 2024-03-24 16:50 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 Next › Last »

xantares commented on 2018-07-08 22:18 (UTC)

I think I fixed it.

mcerb commented on 2018-07-08 18:15 (UTC) (edited on 2018-07-08 18:22 (UTC) by mcerb)

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...
I also changed the config line in the PKGBUILD to this :

${_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.

xantares commented on 2018-05-17 08:44 (UTC) (edited on 2018-05-17 08:45 (UTC) by xantares)

Indeed, binfmt must be disabled, one way to to this is comment out the wine config:

$ cat /usr/lib/binfmt.d/wine.conf
# Start WINE on Windows executables
#:DOSWin:M::MZ::/usr/bin/wine:

pingplug commented on 2018-05-17 08:20 (UTC)

can not build with wine

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

config.log

configure:10032: checking build system compiler i686-w64-mingw32-gcc
configure:10045: i686-w64-mingw32-gcc conftest.c
configure:10048: $? = 0
../configure: line 10050: ./a.out: No such file or directory
../configure: line 10050: ./b.out: No such file or directory
000d:err:menubuilder:init_xdg error looking up the desktop directory
configure:10055: result: yes
configure:10074: checking for build system preprocessor
configure:10085: i686-w64-mingw32-gcc -E conftest.c
# 1 "conftest.c"
# 1 "<built-in>"
# 1 "<command-line>"
# 1 "conftest.c"
configure:10088: $? = 0
configure:10103: result: i686-w64-mingw32-gcc -E
configure:10110: checking for build system executable suffix
configure:10124: i686-w64-mingw32-gcc conftest.c -o conftest.exe
configure:10127: $? = 0
../configure: line 10129: ./conftest: No such file or directory
configure:10124: i686-w64-mingw32-gcc conftest.c -o conftest,ff8
configure:10127: $? = 0
../configure: line 10129: ./conftest: No such file or directory
configure:10124: i686-w64-mingw32-gcc conftest.c -o conftest
configure:10127: $? = 0
../configure: line 10129: ./conftest: No such file or directory
configure:10137: error: Cannot determine executable suffix

Schala commented on 2014-07-02 17:13 (UTC)

Why would this be a multiple package build if the two conflict with each other? It was better off before.

Schala commented on 2013-10-11 13:35 (UTC)

I am not merging this and the static package. They cannot coexist

« First ‹ Previous 1 2 3 Next › Last »