----- Original Message ----- From: "Torbjorn Granlund" Dropping mingw-users from the CC's.
> I have tested this on an Intel Nehalem, running windoze 7 with cygwin and > the mingw compilers. It would be great if people could test > > configure && make && make check During make check: ############################ libtool: link: x86_64-w64-mingw32-gcc -O2 -pedantic -m64 -std=gnu99 -mtune=k8 -march=k8 -o t-locale.exe t-locale.o ../../tests/.libs/libtests.a /c/_64/comp/gmp-5.0.90-20110704/.libs/libgmp.a ../../.libs/libgmp.a c:/_64/alt/bin/../lib/gcc/x86_64-w64-mingw32/4.7.0/../../../../x86_64-w64-mingw32/lib/../lib/libmsvcrt.a(digcs01031.o):(.text+0x0): multiple definition of `localeconv' t-locale.o:t-locale.c:(.text+0x0): first defined here collect2: ld returned 1 exit status make[4]: *** [t-locale.exe] Error 1 make[4]: Leaving directory `/c/_64/comp/gmp-5.0.90-20110704/tests/misc' make[3]: *** [check-am] Error 2 make[3]: Leaving directory `/c/_64/comp/gmp-5.0.90-20110704/tests/misc' make[2]: *** [check-recursive] Error 1 make[2]: Leaving directory `/c/_64/comp/gmp-5.0.90-20110704/tests' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/c/_64/comp/gmp-5.0.90-20110704' make: *** [check] Error 2 ################################# That's the same error as I get with gmp-5.0.2. > You should get assembly code for any 32-bit build, but no assembly code > for any 64-bit build. Checking if assembly code was inclded is most > easily done with an "ls -l mpn/*.asm" after configure. With assembly, > you should see dozens of files, else you should see nothing. No asm files to be found. I'm on Vista64 and I use a 64-bit compiler that was built by the mingw64 team as one of the "automated builds". It's executables (gcc, g++, ar, nm, etc.) are all prefixed with "x86_64-w64-mingw32-". Therefore, my configure command becomes: $ ./configure 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 (That's the same as the 'configure' command I've been running on recent gmp releases, where all has worked fine ... apart from the "locale" issue, which I've simply ignored.) Here's my "gcc -v": ##################################### $ x86_64-w64-mingw32-gcc -v Using built-in specs. COLLECT_GCC=c:\_64\alt\bin\x86_64-w64-mingw32-gcc.exe COLLECT_LTO_WRAPPER=c:/_64/alt/bin/../libexec/gcc/x86_64-w64-mingw32/4.7.0/lto-wrapper.exe Target: x86_64-w64-mingw32 Configured with: ../../../build/gcc/src/configure --target=x86_64-w64-mingw32 --prefix=/c/bb/vista64-mingw32/mingw-x86-x86_64/build/build/root --with-sysroot=/c/bb/vista64-mingw32/mingw-x86-x86_64/build/build/root --enable-languages=all,obj-c++ --enable-fully-dynamic-string --disable-multilib Thread model: win32 gcc version 4.7.0 20110410 (experimental) (GCC) ##################################### BTW, I'm delighted that you are working on providing some assembler routines for the Win64 build of gmp. Thank you for doing that. Cheers, Rob ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
