[issue31359] `configure` script incorrectly detects symbols as available on Mac w/ Xcode 8+

Ronald Oussoren added the comment: This is fixed in bpo-41100 -- dependencies: -Build failure on macOS 11 (beta) resolution: -> fixed stage: -> resolved status: open -> closed superseder: -> Build failure on macOS 11 (beta) ___ Python tracker <

[issue31359] `configure` script incorrectly detects symbols as available on Mac w/ Xcode 8+

Ronald Oussoren added the comment: Added 41100 as a dependency because the active PR for that issue will fix this issue as well. -- dependencies: +Build failure on macOS 11 (beta) ___ Python tracker ___

[issue31359] `configure` script incorrectly detects symbols as available on Mac w/ Xcode 8+

Maxime Belanger added the comment: That'd be even better :). I'll also note that this is slightly worse in Python 3 vs Python 2 as there are way more of these to deal with. -- ___ Python tracker __

[issue31359] `configure` script incorrectly detects symbols as available on Mac w/ Xcode 8+

Ronald Oussoren added the comment: An alternative solution, which is more invasive is to explicitly use weak linking, as is already used for some ancient APIs in posixmodule.c (look for "lchown" in Modules/posixmodule.c). This is more invasive, but would be helpful for upstream as well because

[issue31359] `configure` script incorrectly detects symbols as available on Mac w/ Xcode 8+

Changes by Maxime Belanger : -- components: +Build, macOS nosy: +ned.deily, ronaldoussoren type: -> compile error ___ Python tracker ___

[issue31359] `configure` script incorrectly detects symbols as available on Mac w/ Xcode 8+

New submission from Maxime Belanger: At Dropbox, we use a custom fork of Python to deploy our Desktop Client onto various platforms, including macOS. We currently use the Mac OS X 10.11 SDK, but are considering updating to the macOS 10.12 SDK, which introduced new low-level functions, such as