Re: UINTPTR_MAX, INTPTR_MAX requirements

[Thien-Thi Nguyen]

   From: Dave Love <address@hidden>
   Date: 28 Jan 2002 13:38:19 +0000

   ${ac_dA}HAVE_UINTPTR_T${ac_dB}HAVE_UINTPTR_T${ac_dC}1${ac_dD}
   ${ac_dA}HAVE_PTRDIFF_T${ac_dB}HAVE_PTRDIFF_T${ac_dC}1${ac_dD}
   ${ac_uA}HAVE_UINTPTR_T${ac_uB}HAVE_UINTPTR_T${ac_uC}1${ac_uD}
   ${ac_uA}HAVE_PTRDIFF_T${ac_uB}HAVE_PTRDIFF_T${ac_uC}1${ac_uD}

   I'm not sure how that helps.  If you're going to use the ..._MAX
   macros, a configure test needs to be added, along with fallback
   definitions.

true.  i asked this because i was hoping to see something like:
       
${ac_dA}SIZEOF_UINTPTR_T${ac_dB}SIZEOF_UINTPTR_T${ac_dC}4${ac_dD}
${ac_dA}SIZEOF_PTRDIFF_T${ac_dB}SIZEOF_PTRDIFF_T${ac_dC}4${ac_dD}
${ac_uA}SIZEOF_UINTPTR_T${ac_uB}SIZEOF_UINTPTR_T${ac_uC}4${ac_uD}
${ac_uA}SIZEOF_PTRDIFF_T${ac_uB}SIZEOF_PTRDIFF_T${ac_uC}4${ac_uD}

which would confirm that you are on the HEAD branch.  the output posted
above seems to indicate that you are on the 1.6 branch, but that doesn't
require UINTPTR_MAX.  perhaps a fresh autogen.sh + configure run would
help...

in the meantime, i'll add those tests.  thanks for the tip.

thi