Hi David,
I only support Visual Studio builds so I am afraid that we need someone who
uses the cyggwin/mingw/mingw64 builds to help you with this.
I have just done a fairly major update to mpir-exp in SVN but I don't think
this will help with your problem. For others I do recommend that this
revised version is used.
To help with debugging and testing, here are the changes that I have made
in mpir-exp relative to mpir (both in SVN):
1. Two new types have been introduced for use as the integers in all MPIR
ui/si functions. These are called gmp_ui and gmp_si
2. All ui/si functions have been changed to use these new types
3. These types are set to long types except on Windows x64 where they are
set to long long types.
4. The ui/si functions have been reviewed to ensure that internal integer
variables are of the right length
5: 4 new functions have been added mpf_fits_ui, mpf_fits_si, mpz_fits_ui
and mpz_fits_si
I have also made an unrelated change, which is intended to ensure that the
move to Visual Studio 11 will go smoothly:
1. The output directories that used to be mpir\build.vc10\dll and
mpir\build.vc10\lib are now mpir\dll and mpir\lib
Provided that build tools use my prebuild and postbuild batch files, this
change should be transparent.
I have also improved the python build generator to ensure that its output
is compatible with Visual Studio 11.
Brian
--
You received this message because you are subscribed to the Google Groups
"mpir-devel" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/mpir-devel/-/uvC_TG2t_G8J.
To post to this group, send email to mpir-devel@googlegroups.com.
To unsubscribe from this group, send email to
mpir-devel+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/mpir-devel?hl=en.
