homepage

> 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.
Yes, I can reproduce this in 2.7, 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.)
Same here. It looks like a bug in autoconf:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=560105
My output is below:
"""
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
"""
> 3. Do you know which header file declares uint32_t on FreeBSD 4?
They are declared in inttypes.h.
"""
/*
 * This file is in the public domain.
 * $FreeBSD: src/sys/sys/inttypes.h,v 1.2 1999年08月28日 00:51:47 peter Exp $
 */
#ifndef _SYS_INTTYPES_H_
#define _SYS_INTTYPES_H_
#include <machine/ansi.h>
typedef __int8_t int8_t;
typedef __int16_t int16_t;
typedef __int32_t int32_t;
typedef __int64_t int64_t;
typedef __uint8_t uint8_t;
typedef __uint16_t uint16_t;
typedef __uint32_t uint32_t;
typedef __uint64_t uint64_t;
typedef __intptr_t intptr_t;
typedef __uintptr_t uintptr_t;
#endif /* !_SYS_INTTYPES_H_ */
"""