Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork33.3k
bpo-41100: add runtime checks for MACOSX_DEPLOYMENT_TARGET=10.10#21576
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
bpo-41100: add runtime checks for MACOSX_DEPLOYMENT_TARGET=10.10#21576
Uh oh!
There was an error while loading.Please reload this page.
Conversation
In order to support a universal2 build, supporitng Mac OS 11 on arm64 and Mac OS onx86_64 going back to 10.10, we need to add in runtime checks for functions that willbe detected as present by autoconf, because they are in the SDK, but which did notexist in Mac OS 10.10. This fixes all the instances of -WWunguarded-availability-newwhen building with MACOSX_DEPLOYMENT_TARGET=10.10
lawrence-danna-apple commentedJul 21, 2020
oops, this isn't quite right yet. |
gh-doot commentedJul 21, 2020
im just new to github.. what does that mean? |
lawrence-danna-apple commentedJul 21, 2020
OK it's fixed now |
| #defineHAVE_PREADV_RUNTIME __builtin_available(macos 10.16, ios 14, tvos 14, watchos 7, *) | ||
| #defineHAVE_PWRITEV_RUNTIME __builtin_available(macos 10.16, ios 14, tvos 14, watchos 7, *) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Curious, what is the proper way to detect Big Sur,10.16 or11?
sumanthratnaJul 21, 2020 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
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 likeuio.h, and will be recognized by_builtin_available. I just copied 10.16 out ofuio.h, but it's confusing so I'll change it to 11.0.
lawrence-danna-apple commentedJul 21, 2020
superseded by#21577 |
Uh oh!
There was an error while loading.Please reload this page.
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