-
-
Notifications
You must be signed in to change notification settings - Fork 30.9k
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error during build on unguarded use of new symbols on macOS #128135
Comments
Here's an initial patch 36c7da4 I'm not sure if we should be using I'm having a hard time reproducing failures without cross-compiling via |
Another complexity is astral-sh/python-build-standalone#210 / astral-sh/python-build-standalone#422 — if this is in the |
Perhaps this is dumb to ask, but.. this flag is clang only? I don't think there's an obvious equivalent in gcc? |
I'm not aware of an equivalent one for gcc. Btw, I think we already had an issue for this one: #100384 but I think it's better to keep the latest in this case unless you want to move the discussion out there. |
Ah thank you @picnixz — I don't have a preference for which issue we use but agree it makes sense to close one of them. |
Let's move the discussion on the original one. I'll edit the issue to include your findings. |
Feature or enhancement
Proposal:
CPython builds run against the latest macOS version and unguarded use of new symbols does not throw an error. However, building CPython on older versions of macOS is supported. Consequently, regressions are not caught, e.g.:
aligned_alloc
availability on macOS #128134ptsname_r
is not checked at runtime on macOS #123797Enabling
-Werror=unguarded-availability-new
would be great to catch these before they become a problem downstream.Has this already been discussed elsewhere?
This is a minor feature, which does not need previous discussion elsewhere
Links to previous discussion of this feature:
This was discussed briefly in Discord
The text was updated successfully, but these errors were encountered: