➜

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 njs
Recipients benjamin.peterson, lukasz.langa, martin.panter, ncoghlan, ned.deily, njs, rgbecker, steven.daprano, tds333, thewtex, vstinner
Date 2016-10-14.16:47:48
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1476463668.63.0.414964480668.issue28092@psf.upfronthosting.co.za>
In-reply-to
Content 
Yeah, the config.log there clearly shows that configure is using gcc 4.8.2 on the failed builds. Very odd.

Stepping back for a moment, is there any point in continuing to debug this? Given Benjamin's comment up-thread:

> I mainly converted them to see if it would cause problems

My impression is that restricting inline functions to 'static inline' only is the best plan for 3.6 anyway, since AFAIK that really does work on all the compilers that people are likely to run into, while non-static inline has problems with the default compilers on both CentOS 5 and OS X.
History
Date User Action Args
2016-10-14 16:47:48njssetrecipients: + njs, rgbecker, ncoghlan, tds333, vstinner, benjamin.peterson, ned.deily, steven.daprano, thewtex, lukasz.langa, martin.panter
2016-10-14 16:47:48njssetmessageid: <1476463668.63.0.414964480668.issue28092@psf.upfronthosting.co.za>
2016-10-14 16:47:48njslinkissue28092 messages
2016-10-14 16:47:48njscreate