"Sisyphus" <[email protected]> writes:
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.
Oops, one patch had been omitted (although the change log claimed it was
there). You should have more luck with this snapshot:
ftp://gmplib.org/pub/snapshot/gmp-5.0.90-20110706.tar.bz2
No asm files to be found.
Good.
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
Somewhat tedious, I made some symlink to keep the configure line sane.
BTW, I'm delighted that you are working on providing some assembler
routines for the Win64 build of gmp.
That's next. First, I'd like to understand better the target, and
improve the configure state wrt mingw/cygwin.
I need help with:
* Making sure the new snapshot works for the various mingw and cygwin
32-bit and 64-bit installs. Does asm get properly included for 32-bit
builds, and properly *excluded* for 64-bit builds? Is the exact CPU
used for the host (i.e., not generic things like i386, i686, x86_64)?
* Understanding why --enable-cxx fails. It is related to the absense of
iostream as a shared libtrary. But what can be done about that?
--
Torbjörn
------------------------------------------------------------------------------
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
