Mark Dickinson <dicki...@gmail.com> added the comment: Thanks for the report. Some questions:
1. Have you tested this with Python 3.x at all? I'd expect the same issues to show up for Python 3.1 and 3.2. 2. Also, do you have the relevant configure output to hand? On my machine, the output from './configure' includes: checking for uint32_t... yes checking for uint64_t... yes checking for int32_t... no checking for int64_t... no checking for ssize_t... yes what do you get here? (Aside: those .... 'no's look odd to me; I think there may be an autoconf bug here.) 3. Do you know which header file declares uint32_t on FreeBSD 4? IIRC, the theory is that if stdint.h or inttypes.h #defines/typedefs uint32_t, then the UINT32_T_MAX macro should also be #defined somewhere in one of those header files; OTOH if neither stdint nor inttypes includes declarations for uint32_t then the configure script should find something suitable, and #define uint32_t. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue10052> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
