[issue23644] g++ module compile fails with ‘_Atomic’ does not name a type

2017-07-06 Thread Melroy van den Berg
Melroy van den Berg added the comment: Yea I'm building Python 3.6.1 from source, using gcc and --with-cxx-main=correct/location/to/g++ flag. So the warning message appears during ./configure about that it can't find g++. I didn't try to patch it using the attachments of this

[issue23644] g++ module compile fails with ‘_Atomic’ does not name a type

2017-07-06 Thread Melroy van den Berg
Melroy van den Berg added the comment: Ow sorry, I though it was already fixed in the latest stable version of 3.x. Since is issue is from 2015. -- ___ Python tracker <http://bugs.python.org/issue23

[issue23644] g++ module compile fails with ‘_Atomic’ does not name a type

2017-07-06 Thread Melroy van den Berg
Melroy van den Berg added the comment: I also got this problem with gcc/g++ version 4.9.3. ./Include/pyatomic.h:37:5: error: 'atomic_int' does not name a type I'm using Python 3.6.1. It's not fixed! ------ nosy: +Melroy van den Berg versions: +Py