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 djc
Recipients djc, jfinkels, theller
Date 2010-10-19.16:25:19
SpamBayes Score 0.00978485
Marked as misclassified No
Message-id <1287505524.5.0.859185793242.issue10036@psf.upfronthosting.co.za>
In-reply-to
Content
Current Ubuntu builds from the buildbot also only show the libffi warning:

http://www.python.org/dev/buildbot/builders/x86%20Ubuntu%20Shared%203.x/builds/2326/steps/compile/logs/warnings

I suspect we don't really fix libffi compile warnings because (a) libffi is just bundled from upstream in python, for ctypes, AFAICT, and (b) libffi maintenance seems to be intermittent at best. For example, it seems like we're not bundling any released version of libffi, but just some snapshot from the upstream repo.
History
Date User Action Args
2010-10-19 16:25:24djcsetrecipients: + djc, theller, jfinkels
2010-10-19 16:25:24djcsetmessageid: <1287505524.5.0.859185793242.issue10036@psf.upfronthosting.co.za>
2010-10-19 16:25:20djclinkissue10036 messages
2010-10-19 16:25:20djccreate