On Sunday 26 June 2011 12:50:52 Jeff Gilchrist wrote: > Here is report by a GMP-ECM user that uses MPIR about a strange effect > when trying to compile on mingw64 without giving it a CPU hint. Not > sure if this is a mingw thing or something that can be fixed in the > config script. > > The original post: > http://www.mersenneforum.org/showpost.php?p=264649&postcount=253 > > Summary: > > "I use: > ./configure --build=penryn-w64-mingw32 --host=penryn-w64-mingw32 > --enable-gmpcompat > it doesn't work for me without --enable-gmpcompat. >
ECM needs the library and header files to called libgmp and gmp.h so the enable-gmpcompat switch is necessary. > ./config.guess in MPIR always gives the best cpu it seems, but I > noticed if I didn't use --build and --host it uses i686-pc-mingw32 > further down: > > $ ./config.guess > penryn-w64-mingw32 > > $ ./configure --enable-gmpcompat > checking build system type... penryn-w64-mingw32 > checking host system type... penryn-w64-mingw32 > checking for a BSD-compatible install... /bin/install -c > checking whether build environment is sane... yes > . > . > checking for msgmerge... no > checking build system type... i686-pc-mingw32 > checking host system type... i686-pc-mingw32 > checking for ld used by GCC... c:/mingw64/x86_64-w64-mingw32/bin/ld.exe > checking if the linker (c:/mingw64/x86_64-w64-mingw32/bin/ld.exe) is > GNU ld... yes" I guess is this is due to gcc.exe being a 32bit compiler , whereas the 64bit compiler is called x86-64-w64-mingw32-gcc.exe , when using a cross compiler you basically have to specify everything Alternatively see this thread http://groups.google.com/group/mpir- devel/browse_thread/thread/3aafeb376e39fa99# Jason -- You received this message because you are subscribed to the Google Groups "mpir-devel" group. To post to this group, send email to mpir-devel@googlegroups.com. To unsubscribe from this group, send email to mpir-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/mpir-devel?hl=en.
