[issue20767] Some python extensions can't be compiled with clang 3.4
Kubilay Kocak
report at bugs.python.org
Wed Jan 31 02:48:49 EST 2018
Kubilay Kocak <koobs.freebsd at gmail.com> added the comment:
The changeset(s) applied in this issue were/are fine (thus no response on the issue)
It is the *removal* of the changesets included in this issue (as proposed in https://github.com/python/cpython/pull/5233) that would re-break compilation of extensions with clang (requiring re-opening this issue)
The root cause of the current confusion is the special case added here was conditional on the OS ('freebsd'), whereas it should (arguably) have been for a specific compiler (clang).
In order to do this, this leads to the compiler detection code requiring improvement, see: https://github.com/python/cpython/pull/5233#issuecomment-358906977 as it currently does not detect clang as the default compiler (cc), see: https://github.com/python/cpython/pull/5233#issuecomment-358948425
----------
_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue20767>
_______________________________________
More information about the Python-bugs-list
mailing list