On 12/15/2011 5:47 PM, Sisyphus wrote:
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
I was surprised to find that yes './configure --enable-gmpcompat' works for me,
and it decided on:
configure:3022: checking build system type
configure:3036: result: core2-w64-mingw32
configure:3056: checking host system type
configure:3069: result: core2-w64-mingw32
This never worked for me with GMP (it kept picking i686) so I didn't think to
try it here. Thanks for reminding me to check that.
However, I still get the problem with the t-printf test failing saying:
PASS: t-locale.exe
FAIL: t-printf.exe
PASS: t-scanf.exe
=============================================================
1 of 3 tests failed
See tests/misc/test-suite.log
And in the test-suite.log is the following:
gmp_vsprintf wrong
fmt |%Mu|
got |4294967295|
want |8589934591|
got_len 10
want_len 10
I wonder why the test works in your environment? Maybe the mingw64
cross-compiler can print the posix modifiers by default? Or you may have a
different build, with different options compiled in, than I have? I'm using the
personal build by sezero, the one that was released on 2010-10-03. If you let
me know which build you are using, I can go ask on the mingw64 mailing list.
Are you by any chance compiling in a cygwin environment? I think printf would
work differently there and actually recognize the %llu modifier.
-David C.
--
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.
