[issue36231] no "proper" header files on macOS 10.14 Mojave

2019-06-20 Thread Ned Deily
Ned Deily added the comment: New changeset c421c66a58a6caae30f0679d7e61411418e67cec by Ned Deily in branch '2.7': bpo-36231: Support building on macOS without /usr/include (GH-13773) (GH-14256) https://github.com/python/cpython/commit/c421c66a58a6caae30f0679d7e61411418e67cec --

[issue36231] no "proper" header files on macOS 10.14 Mojave

2019-06-19 Thread Ned Deily
Change by Ned Deily : -- pull_requests: +14086 pull_request: https://github.com/python/cpython/pull/14256 ___ Python tracker ___

[issue36231] no "proper" header files on macOS 10.14 Mojave

2019-06-19 Thread Ned Deily
Change by Ned Deily : -- versions: +Python 2.7, Python 3.7 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue36231] no "proper" header files on macOS 10.14 Mojave

2019-06-19 Thread Ned Deily
Ned Deily added the comment: Thank you again for the suggested PR. Using "xcrun --show-sdk-path" at configure time *is* appealing. Unfortunately, it does not cover all of the necessary use cases. One, the --show-sdk-path option is not available on old versions of xcrun, versions we still

[issue36231] no "proper" header files on macOS 10.14 Mojave

2019-06-19 Thread Jeroen Demeyer
Change by Jeroen Demeyer : -- nosy: +jdemeyer ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue36231] no "proper" header files on macOS 10.14 Mojave

2019-06-19 Thread Dmitrii Pasechnik
Dmitrii Pasechnik added the comment: I find it puzzling that a relatively clean and short solution using autotools and the Apple-approved way to get the location of the headers is rejected, and a hacky, longer way that scrapes output of the compiler is being pushed instead. --

[issue36231] no "proper" header files on macOS 10.14 Mojave

2019-06-18 Thread Ned Deily
Ned Deily added the comment: New changeset c7302116573d853d3181133477d9d0e4d4d3abfd by Ned Deily in branch '3.7': bpo-36231: Support building on macOS without /usr/include (GH-13773) (GH-14208) https://github.com/python/cpython/commit/c7302116573d853d3181133477d9d0e4d4d3abfd --

[issue36231] no "proper" header files on macOS 10.14 Mojave

2019-06-18 Thread Ned Deily
Change by Ned Deily : -- pull_requests: +14046 pull_request: https://github.com/python/cpython/pull/14208 ___ Python tracker ___

[issue36231] no "proper" header files on macOS 10.14 Mojave

2019-06-03 Thread Ned Deily
Ned Deily added the comment: New changeset 0288dd6a5192074fcd5aa0db5d3513c3880209ca by Ned Deily in branch 'master': bpo-36231: Support building on macOS without /usr/include (GH-13773) https://github.com/python/cpython/commit/0288dd6a5192074fcd5aa0db5d3513c3880209ca --

[issue36231] no "proper" header files on macOS 10.14 Mojave

2019-06-03 Thread Ned Deily
Change by Ned Deily : -- pull_requests: +13658 pull_request: https://github.com/python/cpython/pull/13773 ___ Python tracker ___

[issue36231] no "proper" header files on macOS 10.14 Mojave

2019-04-14 Thread Dmitrii Pasechnik
Dmitrii Pasechnik added the comment: In case,I have opened PR https://github.com/python/cpython/pull/12825 to provide our solution to this issue. -- ___ Python tracker ___

[issue36231] no "proper" header files on macOS 10.14 Mojave

2019-04-14 Thread Dmitrii Pasechnik
Change by Dmitrii Pasechnik : -- pull_requests: +12750 stage: -> patch review ___ Python tracker ___ ___ Python-bugs-list mailing

[issue36231] no "proper" header files on macOS 10.14 Mojave

2019-03-14 Thread Ned Deily
Ned Deily added the comment: Thanks for the report and for the PR offer but let's hold off on that for the moment: I'm planning to merge a somewhat different approach. -- assignee: -> ned.deily ___ Python tracker

[issue36231] no "proper" header files on macOS 10.14 Mojave

2019-03-14 Thread Dmitrii Pasechnik
Dmitrii Pasechnik added the comment: I won't mind to provide a PR for this. but it is not clear what the goal should be. Is it to build a working OSX Python with as few external to Xcode deps (it seems that only lzma is needed) as possible? --

[issue36231] no "proper" header files on macOS 10.14 Mojave

2019-03-11 Thread Erik Bray
Erik Bray added the comment: Perhaps it would be better if the `xcrun --show-sdk-path` thing were run at configure-time and its result shoved into a variable we can read with sysconfig.get_config_var() -- nosy: +erik.bray ___ Python tracker

[issue36231] no "proper" header files on macOS 10.14 Mojave

2019-03-08 Thread Dmitrii Pasechnik
Dmitrii Pasechnik added the comment: Needless to say, subprocess is most certainly an overkill, something less involved would do the job, without the need for all the module dependencies of subprocess. -- ___ Python tracker

[issue36231] no "proper" header files on macOS 10.14 Mojave

2019-03-08 Thread Dmitrii Pasechnik
New submission from Dmitrii Pasechnik : Neither Xcode nor its command-line tools on macOS 10.14 Mojave come with header files installed in /usr/ and other "normal" directories. This is not documented in https://devguide.python.org/setup/#macos-and-os-x While an extra step to handle this,