Author indygreg
Recipients Alex.Willmer, Peter Petrik, Peter Petrik2, indygreg, jmr, ned.deily, ronaldoussoren
Date 2019-08-13.03:52:12
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1565668332.78.0.792893474176.issue31601@roundup.psfhosted.org>
In-reply-to
Content
I ran into this with PyOxidizer. CPython's `configure` needs to be made aware of the current macOS SDK version and filter out symbols not present in the target macOS version. I worked around it by `undef`'ing some entries from the generated `pyconfig.h` file.

macOS's clang does emit some warnings when it sees symbols that shouldn't be used with the current target version. CPython's build system should consider adding -Werror=unguarded-availability-new to CFLAGS to turn these warnings into errors so they are caught at compile time and not run time. But there should be proper filtering of affected symbols first, otherwise people won't be able to build CPython when targeting older macOS versions.
History
Date User Action Args
2019-08-13 03:52:12indygregsetrecipients: + indygreg, ronaldoussoren, ned.deily, jmr, Alex.Willmer, Peter Petrik, Peter Petrik2
2019-08-13 03:52:12indygregsetmessageid: <1565668332.78.0.792893474176.issue31601@roundup.psfhosted.org>
2019-08-13 03:52:12indygreglinkissue31601 messages
2019-08-13 03:52:12indygregcreate