| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
The new form matches the way we test for other weak symbols (for example in posixmodule.c)
I earlier moved the pragma, but not the comment that explains why it is necessary.
There was a problem hiding this comment.
LGTM.
Oh ok, now with the fixed test if (ffi_closure_free != NULL) {, I get it :-)
Sorry, something went wrong.
|
Thanks @ronaldoussoren for the PR 🌮🎉.. I'm working now to backport this PR to: 3.10, 3.11. |
Sorry, something went wrong.
|
Sorry, @ronaldoussoren, I could not cleanly backport this to 3.10 due to a conflict. |
Sorry, something went wrong.
|
GH-99638 is a backport of this pull request to the 3.11 branch. |
Sorry, something went wrong.
Fix a number of compile errors with GCC-12 on macOS: 1. In pylifecycle.c the compile rejects _Pragma within a declaration 2. posixmodule.c was missing a number of ..._RUNTIME macros for non-clang on macOS 3. _ctypes assumed that __builtin_available is always present on macOS (cherry picked from commit cdde29d) Co-authored-by: Ronald Oussoren <ronaldoussoren@mac.com>
…99638) gh-99337: Fix compile errors with gcc 12 on macOS (GH-99470) Fix a number of compile errors with GCC-12 on macOS: 1. In pylifecycle.c the compile rejects _Pragma within a declaration 2. posixmodule.c was missing a number of ..._RUNTIME macros for non-clang on macOS 3. _ctypes assumed that __builtin_available is always present on macOS (cherry picked from commit cdde29d) Co-authored-by: Ronald Oussoren <ronaldoussoren@mac.com> Co-authored-by: Ronald Oussoren <ronaldoussoren@mac.com>
| Back | FazBrowse Home | New Git URL |
When compiling with GCC 12 on a macOS 12 system I get three groups of errors: