----- Original Message -----
From: "David Cleaver"
./configure --prefix=C:/_64/mpir --disable-shared --enable-static
--enable-gmpcompat LDFLAGS=-L/c/_64/mpir/lib
CPPFLAGS=-I/c/_64/mpir/include
CC=x86_64-w64-mingw32-gcc CXX=x86_64-w64-mingw32-g++
AR=x86_64-w64-mingw32-ar
LD=x86_64-w64-mingw32-ld NM=x86_64-w64-mingw32-nm
RANLIB=x86_64-w64-mingw32-ranlib OBJDUMP=x86_64-w64-mingw32-objdump
STRIP=x86_64-w64-mingw32-strip
The configure line that I used was:
./configure --build=penryn-w64-mingw32 --host=penryn-w64-mingw32
--enable-gmpcompat
Yes - when configure sees the '--build' and '--host' arguments, it will
decide that this is a cross-compilation and skip the checking of permissible
modifiers - thereby bringing about the failures that you see. (Of course,
that's only if I'm right about this :-)
I can try yours later tonight to see if I get the same results as you.
I use the MinGW64 cross-compiler, where the names of the executables are all
prefixed with 'x86_64-w64-mingw32-'. That is, instead of 'gcc.exe' I have
'x86_64-w64-mingw32-gcc.exe', etc., etc.
If you're not using the cross-compiler, then that command won't work.
I think you probably just need to build without those --build and --host
options.
Does simply './configure --enable-gmpcompat' work ?
You might need to additionally specify 'ABI=64' - that's if configure
doesn't reach that conclusion by itself.
Cheers,
Rob
--
You received this message because you are subscribed to the Google Groups
"mpir-devel" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/mpir-devel?hl=en.
