This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: Test for uintptr_t seems to be incorrect
Type: Stage:
Components: Build Versions: Python 2.5
process
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: Nosy List: loewis, ronaldoussoren
Priority: high Keywords:

Created on 2006-10-01 18:10 by ronaldoussoren, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Messages (2)
msg30096 - (view) Author: Ronald Oussoren (ronaldoussoren) * (Python committer) Date: 2006-10-01 18:10
Someone reported on the pythonmac list that HAVE_UINTPTR_T wasn't 
defined in pyconfig.h while it should have been defined. I'm looking into 
this and am now wondering whether the configure snipped below is 
correct:

AC_MSG_CHECKING(for uintptr_t support)
have_uintptr_t=no
AC_TRY_COMPILE([], [uintptr_t x; x = (uintptr_t)0;], [
  AC_DEFINE(HAVE_UINTPTR_T, 1, [Define this if you have the type 
uintptr_t.])
  have_uintptr_t=yes
])
AC_MSG_RESULT($have_uintptr_t)
if test "$have_uintptr_t" = yes ; then
AC_CHECK_SIZEOF(uintptr_t, 4)
fi

This seems to check for uintptr_t as a builtin type. Isn't one supposed to 
include <stdint.h> to get this type?

Chaning the AC_TRY_COMPILE line to the line below fixes the issue for me 
on OSX and Linux:

AC_TRY_COMPILE([#include <stdint.h>], [uintptr_t x; x = (uintptr_t)0;], [


BTW. This issue is also present in Python 2.4.
msg30097 - (view) Author: Martin v. Löwis (loewis) * (Python committer) Date: 2006-10-02 14:57
Logged In: YES 
user_id=21627

Thanks for the report. fixed in r52086, 52087, 52088.
History
Date User Action Args
2022-04-11 14:56:20adminsetgithub: 44061
2006-10-01 18:10:40ronaldoussorencreate