On Jan 8, 6:03 pm, Bill Hart <goodwillh...@googlemail.com> wrote:
> It's surely as much an issue for them as it is for us. I personally
> would be inclined to discuss the issue with them as they seem like
> reasonable and helpful people.
>
> Of course they aren't going to fix it overnight, whereas we want to
> release as soon as possible. So this is indeed going to be an annoying
> issue for a while.
>
> We may have to not support large sizes until at least MPFR agree to
> the changes. Is it possible to add a single #define to MPIR that
> allows the build to be switched from one to the other easily? That way
> at least users can decide.
I think I've mostly solved it - MPFR didn't like the way I did this -
I've done it a slightly different way and MPFR now seems happy.
MPFR won't print out mp_size_t types correctly because it is using a
%li format code where Windows would require a %lli.
But, other than this, it now seems to work.
Brian
--
You received this message because you are subscribed to the Google Groups
"mpir-devel" group.
To post to this group, send email to mpir-de...@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.
