Repository navigation
Error during build on unguarded use of new symbols on macOS #128135
Description
Activity
- changed the title
[-]Error during build on unguarded use of new symbols[/-][+]Error during build on unguarded use of new symbols on macOS[/+]on Dec 20, 2024 Here's an initial patch 36c7da4
I'm not sure if we should be using
unguarded-availabilityorunguarded-availability-newand define an explicit lower bound version? We use the latter downstream, but we also set a minimum version.I'm having a hard time reproducing failures without cross-compiling via
python-build-standalone. Probably user error.Another complexity is astral-sh/python-build-standalone#210 / astral-sh/python-build-standalone#422 — if this is in the
CFLAGSinsysconfigit is used to build extension modules in some packages which causes failures.Perhaps this is dumb to ask, but.. this flag is clang only? I don't think there's an obvious equivalent in gcc?
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_allocavailability on macOS #128134ptsname_ris not checked at runtime on macOS #123797Enabling
-Werror=unguarded-availability-newwould 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