It seems the problem is UINT_MAX is defined in limits.h not stdint.h. Whilst the latter always includes the former, it seems people include the former without the latter. This occurred to me the other night actually. But I thought I was following standard advice on how to deal with these things, so I didn't check carefully that the advice was correct.
I think I need to check for UINTMAX_MAX, or something that can only be defined by stdint.h. Why on earth does a standard library not include standard header guards in it's header? I mean this stdint.h thing is utterly nuts. Bill. On 13 June 2015 at 18:00, Bill Hart <goodwillh...@googlemail.com> wrote: > > > On 13 June 2015 at 17:55, Jeroen Demeyer <jdeme...@cage.ugent.be> wrote: > >> On 2015-06-11 12:35, 'Bill Hart' via mpir-devel wrote: >> >>> One potential solution would be to have configure substitute macros in >>> gmp-h.in when creating mpir/gmp.h. But this doesn't >>> work when cross compiling. >>> >> I don't quite understand why this doesn't work. I think this is the best >> solution. >> > > How can I know what to substitute for the machine you are cross compiling > for? I can't know if that machine has stdint.h. > > >> >> The problem is that mpir-2.7.0.alpha13 breaks when compiling giac: >> >> In file included from first.h:247:0, >> from input_lexer.ll:51: >> /usr/local/src/sage-config/local/include/gmp.h:1232:2: error: ‘uintmax_t’ >> does not name a type >> __GMP_DECLSPEC uintmax_t mpz_get_ux __GMP_PROTO ((mpz_srcptr)); >> ^ >> >> It seems that UINT32_MAX is defined (I don't know why though), but that >> stdint.h is not included. > > > Ouch. Well that is a problem. > > Apparently there are now zero ways to determine if stdint.h has been > included or is available. > > Whoever invented this stupid stdint thing should be shot. > > Bill. > > >> >> >> -- >> 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. >> > > -- 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.
