On 05/02/11 05:09, Gary V. Vaughan wrote: >> example, it could be that <limits.h> (which intprops.h includes) >> > redefines UINT_FAST8_MAX to the wrong value. > That seems to me to be what is happening. Is this something that gnulib > stdint.h can fix? It looks like a stupid mistake on the part of the > HPUX headers.
The HPUX headers are self-consistent, no? They define UINT_FAST8_MAX to UINT_MAX and uint_fast8_t to unsigned int. The gnulib stdint.h is also self-consistent, using unsigned long int instead. The problem is that somehow they clash. I still don't understand fully how they clash, unfortunately. It appears that the problem is that the gnulib stdint.h defines UINT_FAST8_MAX one way, and HP-UX limits.h another. But I don't see how that could happen, since gnulib stdint.h includes HP-UX limits.h, and then redefines UINT_FAST8_MAX. Could you investigate that?
