I think that the flag should be passed in by the build system, which means flint will probably have to fix this.
However, perhaps there's another workaround worth considering, namely to check if INTMAX_MAX is defined. If not, then exclude the intmax code in that instance too, since we cannot be sure it will work. Now recent autotools may even have a config.h flag to tell whether INTMAX_MAX is defined. We could check that. Bill. On 10 April 2014 11:15, Jean-Pierre Flori <jpfl...@gmail.com> wrote: > > > On Wednesday, April 9, 2014 5:37:54 PM UTC+2, Bill Hart wrote: >> >> Great, I think I will add the following to mpirxx.h and head home for the >> day: >> >> Yeah. > To conclude, I'd say this is a PPL issue, so no action to be taken on the > MPIR side. > Also note this is surely not Cygwin specific. > > -- You received this message because you are subscribed to the Google Groups "mpir-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to mpir-devel+unsubscr...@googlegroups.com. To post to this group, send email to mpir-devel@googlegroups.com. Visit this group at http://groups.google.com/group/mpir-devel. For more options, visit https://groups.google.com/d/optout.
