bpo-41100: add runtime checks for MACOSX_DEPLOYMENT_TARGET=10.10#21576
Closed
lawrence-danna-apple wants to merge 2 commits into
python:masterpython/cpython:masterfrom
lawrence-danna-apple:postback-runtime-checkslawrence-danna-apple/cpython:postback-runtime-checksCopy head branch name to clipboard
Closed
bpo-41100: add runtime checks for MACOSX_DEPLOYMENT_TARGET=10.10#21576lawrence-danna-apple wants to merge 2 commits intopython:masterpython/cpython:masterfrom lawrence-danna-apple:postback-runtime-checkslawrence-danna-apple/cpython:postback-runtime-checksCopy head branch name to clipboard
lawrence-danna-apple wants to merge 2 commits into
python:masterpython/cpython:masterfrom
lawrence-danna-apple:postback-runtime-checkslawrence-danna-apple/cpython:postback-runtime-checksCopy head branch name to clipboard
Conversation
In order to support a universal2 build, supporitng Mac OS 11 on arm64 and Mac OS on x86_64 going back to 10.10, we need to add in runtime checks for functions that will be detected as present by autoconf, because they are in the SDK, but which did not exist in Mac OS 10.10. This fixes all the instances of -WWunguarded-availability-new when building with MACOSX_DEPLOYMENT_TARGET=10.10
Contributor
Author
|
oops, this isn't quite right yet. |
|
im just new to github.. what does that mean? |
Contributor
Author
|
OK it's fixed now |
maxbelanger
reviewed
Jul 21, 2020
Comment on lines
+89
to
+90
| #define HAVE_PREADV_RUNTIME __builtin_available(macos 10.16, ios 14, tvos 14, watchos 7, *) | ||
| #define HAVE_PWRITEV_RUNTIME __builtin_available(macos 10.16, ios 14, tvos 14, watchos 7, *) |
Contributor
There was a problem hiding this comment.
Curious, what is the proper way to detect Big Sur, 10.16 or 11?
There was a problem hiding this comment.
My understanding is that on current macs (with the Intel processor), upgrading to Big Sur will result in 10.16. However, on Apple Silicon, Big Sur will be 11.0.
Contributor
Author
There was a problem hiding this comment.
It's 11.0 for both Intel and Arm, however before the public disclosure it was marked as 10.16, so 10.16 appears in some of the headers like uio.h, and will be recognized by _builtin_available. I just copied 10.16 out of uio.h, but it's confusing so I'll change it to 11.0.
Contributor
Author
|
superseded by #21577 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In order to support a universal2 build, supporting Mac OS 11 on arm64 and Mac OS on
x86_64 going back to 10.10, we need to add in runtime checks for functions that will
be detected as present by autoconf, because they are in the SDK, but which did not
exist in Mac OS 10.10. This fixes all the instances of -WWunguarded-availability-new
when building with MACOSX_DEPLOYMENT_TARGET=10.10
https://bugs.python.org/issue41100