[issue36231] Support builds on macOS without installed system header files

2019-06-20 Thread Dmitrii Pasechnik
Dmitrii Pasechnik added the comment: Thanks for the review of our PR. I think not all points made there are relevant: * on older systems, where `xcrun --show-sdk-path` is not available, one can assume that /usr/include is there, and simply set the corresponding variable to this value in

[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-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 <https://bugs.python.org/issue36

[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 <https://bugs.python.org/issue36231> ___ ___ Python-bugs-lis

[issue36106] resolve sinpi() name clash with libm

2019-04-12 Thread Dmitrii Pasechnik
Dmitrii Pasechnik added the comment: Can this also be backported to 3.5. and 3.6, as requested by FreeBSD maintainers? -- ___ Python tracker <https://bugs.python.org/issue36

[issue36432] Running python test suite fails on macOS 10.14.4 with resource.RLIMIT_STACK error

2019-04-11 Thread Dmitrii Pasechnik
Change by Dmitrii Pasechnik : -- nosy: +dimpase ___ Python tracker <https://bugs.python.org/issue36432> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue36344] install_certificates.command too complicated, copy from pip's dir instead

2019-03-19 Thread Dmitrii Pasechnik
Dmitrii Pasechnik added the comment: The script install_certificates.command depends upon pip, it calls pip to install certifi. Thus it's no less "optional" than pip. And pip is only functional, and it able to do the installation in question, due to it including the certific

[issue36344] install_certificates.command too complicated, copy from pip's dir instead

2019-03-18 Thread Dmitrii Pasechnik
New submission from Dmitrii Pasechnik : Currently (e.g. on the released Python 2.7.16) Mac/BuildScript/resources/install_certificates.command does install certifi module from the net and symlinks its cacert.pem to provide openssl with a working certificate. The same task may be accomplished

[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 pos

[issue34956] _tkinter built on macOS 10.14 does not link to Tcl and Tk in /Library/Frameworks

2019-03-09 Thread Dmitrii Pasechnik
Dmitrii Pasechnik added the comment: On https://bugs.python.org/issue36231 I propose a way to build without creating any symlinks. -- nosy: +dimpase ___ Python tracker <https://bugs.python.org/issue34

[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 <ht

[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

[issue36106] resolve sinpi() name clash with libm

2019-02-26 Thread Dmitrii Pasechnik
Change by Dmitrii Pasechnik : -- pull_requests: +12076 ___ Python tracker <https://bugs.python.org/issue36106> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue36106] resolve sinpi() name clash with libm

2019-02-25 Thread Dmitrii Pasechnik
Dmitrii Pasechnik added the comment: e.g. if I rename `m_lgamma` to `lgamma` I get ``` mathmodule.c:389:1: error: static declaration of ‘lgamma’ follows non-static declaration lgamma(double x) ``` -- ___ Python tracker <https://bugs.python.

[issue36106] resolve sinpi() name clash with libm

2019-02-25 Thread Dmitrii Pasechnik
Dmitrii Pasechnik added the comment: This has a potential header conflict. For the same reason functions like lgamma, etc. are prefixed with `m_` in Modules/mathmodule.c -- ___ Python tracker <https://bugs.python.org/issue36

[issue36106] resolve sinpi() name clash with libm

2019-02-25 Thread Dmitrii Pasechnik
New submission from Dmitrii Pasechnik : The standard math library (libm) may follow IEEE-754 recommendation to include an implementation of sinPi(), i.e. sinPi(x):=sin(pi*x). And this triggers a name clash, found by FreeBSD developer Steve Kargl, who worken on putting sinpi into libm used on