<< Starting New Thread >> On 8/25/2009 07:53, Sisyphus wrote: >> You can build 2.4.x it from source, grab it at <http://www.mpfr.org/>. > > Yes, I already have the source. I guess I could use the provided gmp > binaries to build mpfr, but I would prefer to use a gmp I had built myself. > Also, building my own gmp would enable me to use gmp-4.3.1. > (In any case, I expect the issues I'm facing in trying to build gmp would > still be a stumbling block when it comes to building mpfr.) > >> Did you remember to pass --build/--host to configure? > > No, I didn't. How do I determine the correct values for --build and --host ? >
Hi, Here is what the machine triplet, build, host, and target option does: * machine triplet - The triplet key identifies a platform. Usually comes in the form of "cpu"-"vendor"-"system". * build - Build machine triplet, usually corresponds with native gcc target (gcc -dumpmachine). In this case it is "i686-pc-mingw32". * host - The platform in which you want the library/program you just compiled to run on. You need a cross compiler to this (the mingw-w64 toolchain targeting win64 from sf is a cross compiler). Since you want them to run on win64, it is "x86_64-w64-mingw32". * target - This option is usually unused. It is reserved for compilers, assemblers, or other code generators. It specifies the platform the code generator will produce code for. The toolchain in mingw-w64-bin_i686-mingw_20090819.zip is very old, it uses the "pc" vendor key instead of "w64". I suggest you use one of the automated toolchain builds targeting win64. There has been a lot of bug fixes and feature enhancements since then. If you are trying to rebuild GCC, you can place gmp and mpfr at the root of the GCC source tree as "gmp" and "mpfr" respectively. GCC will pass the correct options to it. If you want them installed as libraries, you should pass "--build=i686-pc-mingw32 --host=x86_64-w64-mingw32" to configure. configure assumes you want a native build if those aren't specified. The configure script from GMP is a bit different, it checks the cpu key to enable assembly optimizations. Due to the different ABI for Linux and win64, it doesn't work yet. Pass "--host=none-none-none 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 ABI=longlong" to build it without assembly optimization. For MPFR, passing just the --build/--host option should work fine. HTH ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
