implement PY_UNSUPPORTED_OPENSSL_BUILD on macOS#100265
implement PY_UNSUPPORTED_OPENSSL_BUILD on macOS#100265mmomtchev wants to merge 2 commits intopython:mainfrom
Conversation
|
Most changes to Python require a NEWS entry. Please add it using the blurb_it web app or the blurb command-line tool. |
✅ Deploy Preview for python-cpython-preview canceled.
|
|
Most changes to Python require a NEWS entry. Please add it using the blurb_it web app or the blurb command-line tool. |
|
Hello, I plan to close the PR in about a month, if there are no objections. |
|
This PR is two years old and the build system used for 3.12 is not the same anymoore. Trusting the people is nice, but understanding the changes is even better. |
|
As you may have seen from my profile, I am currently unemployed because of a huge organized extortion with the help of the French police and many big companies. In order to intimidate me, people are posting simultaneous issues on my projects. Yours is one of these. |
This is an extension for the undocumented and untested (on purpose) feature
PY_UNSUPPORTED_OPENSSL_BUILDfeature for macOSThis is something that is possible on macOS too via an obscure
ld64linker option called-lhidden-lwhich specifies that the static library version is to be included and its symbols are not to be reexported.The macOS
ld64option exists at least since OS X 10.11, butclangsupports it only since 15.0.0, hence the-Wlwhich ensures backwards compatibilityhttps://releases.llvm.org/15.0.0/tools/lld/docs/ReleaseNotes.html
https://opensource.apple.com/source/ld64/ld64-609/doc/man/man1/ld.1.auto.html
PS Apple's own man-page seems to be slightly misleading - this does not work if both the dynamic and the static libraries are installed at this location - I am still looking for a way to select the static library in this case