So probably the problem will go away for them if they upgrade to the latest autotools. It has a test for this and presumably is automatically adding the flag when it is building our own test code.
Bill. On 9 April 2014 16:24, Bill Hart <[email protected]> wrote: > Yeah, as I said, they get defined only if you first do: > > #define __STDC_LIMIT_MACROS 1 > > Bill. > > > On 9 April 2014 16:23, Jean-Pierre Flori <[email protected]> wrote: > >> >> >> On Wednesday, April 9, 2014 4:08:21 PM UTC+2, Bill Hart wrote: >>> >>> So assuming limits.h has been included, we have: >>> >>> MPIR_HAVE_STDINT 1 >>> INTMAX_MAX != LONG_MAX >>> UINTMAX_MAX != ULONG_MAX >>> >>> This is because on Cygwin64 INTMAX_MAX is not defined. Who knows where >>> they put the definition. It's not in stdint.h or limits.h. >>> >>> Strange. >> I do have: >> jp@napoleon-7 /usr/include >> $ grep -r INTMAX . >> ./stdint.h:#define INTMAX_MIN (-__I64(9223372036854775807) - 1) >> ./stdint.h:#define INTMAX_MAX (__I64(9223372036854775807)) >> ./stdint.h:#define UINTMAX_MAX (__U64(18446744073709551615)) >> ./stdint.h:#define INTMAX_C(x) x ## L >> ./stdint.h:#define UINTMAX_C(x) x ## UL >> ./stdint.h:#define INTMAX_C(x) x ## LL >> ./stdint.h:#define UINTMAX_C(x) x ## ULL >> >> and indeed there: >> /* Limits of greatest-width integer types */ >> >> #define INTMAX_MIN (-__I64(9223372036854775807) - 1) >> #define INTMAX_MAX (__I64(9223372036854775807)) >> #define UINTMAX_MAX (__U64(18446744073709551615)) >> >> And I have LONG_MAX in limits.h. >> >> > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/mpir-devel. For more options, visit https://groups.google.com/d/optout.
