Closed GoogleCodeExporter closed 8 years ago
I haven't built with mingw for some time. I'll see if I can look at the errors
this evening.
Original comment by casevh
on 26 Dec 2013 at 4:26
I've reviewed all the compiler warnings and errors in the test suite. The
compiler warnings are all related to debugging code. The warnings shouldn't
impact the normal behavior of gmpy. The errors in the test suite can be
ignored, too. The first error is just identifying the version of GMP and the
test doesn't recognize version 5.1.x. The second error (mpf binio) are mostly
likely related to changes in unspecified behavior of the precision/truncation
of the mpf type.
Just curious, is there a reason you couldn't use the pre-compiled binary
versions?
Original comment by casevh
on 27 Dec 2013 at 1:31
Thank you for your effort and assessment. Good to know these test results
were benign.
As to the pre-compiled(s) - I tried, both gmpy and gmpy2. I generally
expect a package in python27
site_packages to be a folder, for no particular reason than it seems like
they usually are (in windows xp).
So I tried both executables, scrolled down in site-packages only as far as
the end of the folders,
and not seeing a folder for either, concluded they had silently failed due
to some missing, underlying
requirement (i.e. GMP, MPC, MPFR, MPIR) and turned to building what I could
of them in MSYS.
Today I broke through the 'end of folders' barrier, scrolled down, and
indeed both gmpy and gmpy2
were present. So, learn a little more everyday. Sorry to have put you
through an unnecessary effort.
Original comment by englishc...@gmail.com
on 27 Dec 2013 at 3:47
Not a problem. I hope you find gmpy useful.
Original comment by casevh
on 28 Dec 2013 at 2:15
Original issue reported on code.google.com by
englishc...@gmail.com
on 26 Dec 2013 at 1:55