Skip to content

Fix the only non-C90 comment to be C90 compatible. #568

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 8, 2017
Merged

Fix the only non-C90 comment to be C90 compatible. #568

merged 1 commit into from
Mar 8, 2017

Conversation

ndparker
Copy link
Contributor

@ndparker ndparker commented Mar 8, 2017

This is a follow up to #566

(Python 3.6 backport)

@serhiy-storchaka
Copy link
Member

@ned-deily, I think it would be nice to include this simple change in 3.6.1.

@serhiy-storchaka serhiy-storchaka merged commit 51b646a into python:3.6 Mar 8, 2017
ned-deily pushed a commit to ned-deily/cpython that referenced this pull request Mar 21, 2017
telamonian added a commit to telamonian/python-cmake-buildsystem that referenced this pull request Sep 17, 2020
The intel C compiler [defaults to `-std=gnu98`](https://software.intel.com/content/www/us/en/develop/documentation/cpp-compiler-developer-guide-and-reference/top/compiler-reference/compiler-options/compiler-option-details/language-options/std-qstd.html#std-qstd_GUID-338F4C2A-560C-4338-8ACF-C4B022A7C865), which apparently causes problems with recent cpython source. Judging by the existing code in `CMakeLists.txt` and [this issue on the core cpython repo](python/cpython#568), somewhere around cpy3.6 cpython moved on to C99.

This PR ensures that if intel compilers are being used on cpy>=3.6 source, the `-std=C99` flag will be added
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants