Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork 35.2k
gh-109054: configure checks if libatomic is needed#109101
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
Uh oh!
There was an error while loading. Please reload this page.
Changes from all commits
File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,6 @@ | ||
| Fix building the ``_testcapi`` extension on Linux AArch64 which requires | ||
| linking to libatomic when ``<cpython/pyatomic.h>`` is used: the | ||
| ``_Py_atomic_or_uint64()`` function requires libatomic | ||
| ``__atomic_fetch_or_8()`` on this platform. The configure script now checks | ||
| if linking to libatomic is needed and generates a new LIBATOMIC variable | ||
| used to build the _testcapi extension. Patch by Victor Stinner. |
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just realised we could probably just use
${VAR="default"}instead of the more verboseVAR=${VAR-"default"}. However, let's stick to the existing practise :) And hopefully,configure.acisgit rm'd some day.