Sorry, something went wrong.
| elif archs == ('arm64', 'x86_64'): | ||
| machine = 'universal2' |
There was a problem hiding this comment.
@ronaldoussoren I'm uncertain whether I should leave in the changes to allow universal2? I don't believe Homebrew requires this, nor would we (Dropbox).
I also don't think universal2 would be very practical given I am not back porting the weak linking changes.
Sorry, something went wrong.
|
We have less than a week to merge this before 3.8 goes into security fixes only mode. |
Sorry, something went wrong.
|
Thanks, @maxbelanger! As noted in bpo-41100, the contents of this PR have been rolled up into #25806. When that PR is resolved, we can close this one. |
Sorry, something went wrong.
|
Thanks for getting this over the finish line, @ned-deily! |
Sorry, something went wrong.
This is a partial backport of bpo-41100 changes e8b1c038b14b5fc8120aab62c9bf5fb840274cb6 and 96d906b144e6e6aa96c5ffebecbcc5d38034bbda for Python 3.8. We introduce the ability to build Python from source for arm64 on macOS, but we do not make a promise of support. This allows us to omit support for weak-linking of symbols from the macOS SDK based on the deployment target, which are larger changes much more difficult to merge.
This also includes a backport of subsequent bpo-42688 change 7e729978fa08a360cbf936dc215ba7dd25a06a08 to fix build errors with external libffi.
https://bugs.python.org/issue41100