Author rakeller
Recipients Glenn Johnson, Saszalez, cberger, rakeller, skrah, vstinner
Date 2019-09-27.15:14:39
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1569597280.02.0.333911115217.issue37415@roundup.psfhosted.org>
In-reply-to
Content
We have been experiencing the same problem with compiling Python-3.7.4 on a system with CentOS 7.6 (aka glib-2.17): Intel Compiler 2019.6 implements stdatomic.h. but lacks the definition of atomic_uintptr_t.

From a configure-point of view just failing to define HAVE_STDATOMIC_H would suffice.
Therefore just add another otherwise unused variable (which might warn & bail out in case of -Werror / -Werror-all)...

The following patch works for us to compile.

Granted, the "proper" way would be to add another configure check for the underlying type and not blurry the check for stdatomic.h -- but then again, Intel should just implement all of C11...
History
Date User Action Args
2019-09-27 15:14:40rakellersetrecipients: + rakeller, vstinner, skrah, cberger, Saszalez, Glenn Johnson
2019-09-27 15:14:40rakellersetmessageid: <1569597280.02.0.333911115217.issue37415@roundup.psfhosted.org>
2019-09-27 15:14:39rakellerlinkissue37415 messages
2019-09-27 15:14:39rakellercreate