I will test for INTMAX_MAX. By my reading of the "standard", this "shall" be defined, if the user of stdint.h made all the necessary incantations.
http://pubs.opengroup.org/onlinepubs/000095399/basedefs/stdint.h.html Bill. On 13 June 2015 at 20:30, Bill Hart <goodwillh...@googlemail.com> wrote: > > > On 13 June 2015 at 19:24, Jeroen Demeyer <jdeme...@cage.ugent.be> wrote: > >> On 2015-06-13 18:00, 'Bill Hart' via mpir-devel wrote: >> >>> 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. >>> >> I think you can assume that the build environment is sufficiently similar >> to the host environment. > > > I don't. Cross compilation is often done when the build machine is very > different, usually because it is much faster and has way more stuff on it. > > >> Normally, when cross-compiling, you are supposed to use the header files >> for the host environment anyway. >> > > I don't see how you could do that. > > >> >> I would also guess that people who cross-compile MPIR are more likely to >> cross-compile other pieces of software against the cross-compiled MPIR. >> >> There would only be a problem if >> 1) MPIR is cross-compiled, and >> 2) Some other package is compiled on the host machine using the >> cross-compiled MPIR, and >> 3) The build system has <stdint.h> but the host system does not. > > > Precisely. This is what breaks. It's clearly the incorrect solution. > > What I suggested is the right solution. It's just the execution that is > the problem. Speaking of executions, we should restart the schedule at > dawn, if not before, starting with the people who came up with stdint.h in > the first place. > > I'll change the test to look for INTMAX_MAX now, as soon as I check the > standard to ensure this *must* be defined in stdint.h. I relied on some > idiot on the interwebs who said you are supposed to check for UINT32_MIN, > the only one that isn't defined. Someone else said that should be > UINT32_MAX. They were wrong too.... > > 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.
