Nathaniel Smith added the comment:

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.


Python tracker <>
Python-bugs-list mailing list

Reply via email to