What GCC version had <stdint.h> defined?

["Martin v. Löwis"]

Scott David Daniels wrote:
> The problem is, of course (Billy G is always a problem), that I am running
> on Win2K, so I don't run configure.in.  I have two copies of MinGW --
> one 2.95 (no stdint.h), and one 3.2.3 which does do stdint.h.
> These were not set up when whoever built windows 2.3.4 did so -- he or
> she did not know what was going to be on my disk after I downloaded and
> installed python.

Can you please explain what the problem is that you are trying to solve?
Apparently, it is not compiling Python.

If you are trying to compile a Python extension, can't you just check
for presence of /usr/include/stdint.h in setup.py?

But then, if you are compiling an extension - why do you even *need*
to know whether stdint.h is present?

Regards,
Martin