➜

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.

Author vstinner
Recipients Devin Jeanpierre, mark.dickinson, skrah, vstinner
Date 2013-05-01.19:35:48
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1367436948.49.0.516911816398.issue17884@psf.upfronthosting.co.za>
In-reply-to
Content 
> I *think* that since the issue #10052 fix, the current autoconf
> machinery is now fairly good at finding those types across platforms,
> but I wouldn't want to make any bets.

The issue #10052 was not that the int32_t was not present, but an #ifdef issue: "This error occurs when HAVE_UINT32_T or HAVE_INT32_T are not defined".

I don't understand why "#ifdef HAVE_UINT32_T" is tested, since configure ensures that uint32_t is always defined. (If it is not, it is defined in pyconfig.h using a #define.)
History
Date User Action Args
2013-05-01 19:35:48vstinnersetrecipients: + vstinner, mark.dickinson, Devin Jeanpierre, skrah
2013-05-01 19:35:48vstinnersetmessageid: <1367436948.49.0.516911816398.issue17884@psf.upfronthosting.co.za>
2013-05-01 19:35:48vstinnerlinkissue17884 messages
2013-05-01 19:35:48vstinnercreate