Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

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

Conversation

@lawrence-danna-apple
Copy link
Contributor

@lawrence-danna-applelawrence-danna-apple commentedJul 21, 2020
edited by bedevere-bot
Loading

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

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
Copy link
ContributorAuthor

oops, this isn't quite right yet.

@gh-doot
Copy link

im just new to github.. what does that mean?

@lawrence-danna-applelawrence-danna-apple deleted the postback-runtime-checks branchJuly 21, 2020 05:57
@lawrence-danna-apple
Copy link
ContributorAuthor

OK it's fixed now

Comment on lines +89 to +90
#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, *)
Copy link
Contributor

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?

Copy link

@sumanthratnasumanthratnaJul 21, 2020
edited
Loading

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.

Copy link
ContributorAuthor

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
Copy link
ContributorAuthor

superseded by#21577

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@abalkinabalkinAwaiting requested review from abalkin

@pgansslepganssleAwaiting requested review from pganssle

@tirantiranAwaiting requested review from tiran

2 more reviewers

@maxbelangermaxbelangermaxbelanger left review comments

@sumanthratnasumanthratnasumanthratna left review comments

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

6 participants

@lawrence-danna-apple@gh-doot@maxbelanger@sumanthratna@the-knights-who-say-ni@bedevere-bot

[8]ページ先頭

©2009-2025 Movatter.jp