What GCC version had <stdint.h> defined?
jepler at unpythonic.net
Fri Aug 27 04:26:43 CEST 2004
I glanced at configure.in and it checks for HAVE_UINTPTR_T, but not
HAVE_INTPTR_T. If you want this define where it's available, add the
proper test to configure.in and regenerate configure.
I think the block would be something like this, a straightforward
search-and-replace of the block for HAVE_UINTPTR_T:
AC_MSG_CHECKING(for intptr_t support)
AC_TRY_COMPILE(, [intptr_t x; x = (intptr_t)0;], [
AC_DEFINE(HAVE_INTPTR_T, 1, [Define this if you have the type
if test "$have_intptr_t" = yes ; then
on the other hand, maybe this test is broken, because my system (Fedora
Core 2) configured with #undef HAVE_UINTPTR_T.
Maybe this article shows the way:
AC_MSG_CHECKING(for uintptr_t in C library)
[uintptr_t foo = 0;
if test $gdb_cv_have_uintptr_t = yes; then
... with appropriate renaming for Python.
I'm not sure why uintptr_t or intptr_t are all that useful, since the
spellings "unsigned *" and "int *" are going to work everywhere anyway.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 196 bytes
Desc: not available
More information about the Python-list