-
Notifications
You must be signed in to change notification settings - Fork 242
Build error on macOS ARM no GIL #857
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
Comments
CFFI does not support freethreaded Python at this point, so this is not expected to work, see: python-cffi/cffi#119 |
If I force the build to use our fork of CFFI: diff --git a/pyproject.toml b/pyproject.toml
index d6cc581..5c91e55 100644
--- a/pyproject.toml
+++ b/pyproject.toml
@@ -3,7 +3,7 @@
requires = [
"setuptools>=61.0.0,!=74.0.0",
"wheel",
- "cffi>=1.4.1; platform_python_implementation != 'PyPy'",
+ "cffi @ git+https://github.com/quansight-labs/cffi; platform_python_implementation != 'PyPy'",
]
build-backend = "setuptools.build_meta" After updating from I can build and run the tests on the free-threaded build. I don't see any test failures. It would probably be helpful for our effort to upstream the changes in our fork of cffi if we could come up with multithreaded tests. Mostly to stress-test cffi. |
I tried building pynacl with TSAN support but hit a build error in libsodium's
I don't see an upstream issue mentioning TSAN so maybe no one has hit this before. |
That test file has a warning in it if you try to compile with asan and appears to be doing a bunch of signal handler testing. |
I opened jedisct1/libsodium#1450. I might hack the libsodium build to ignore that error to see if I can run a test I wrote under TSAN that encrypts a message in chunks in a thread pool as well as the full test suite under pytest-run-parallel. The latter is imperfect because it will skip tests using hypothesis because hypothesis isn't thread-safe. |
I ended up finding some races in our fork of CFFI (Quansight-Labs/cffi#2 (comment)). Nothing worrying and nothing that's problematic on the GIL-enabled build. Thanks for sanity checking what I was seeing earlier @reaperhulk. |
Attempting to build on Python 3.14t on macOS on ARM, I get the following failure:
This may or may not be related to #834.
The text was updated successfully, but these errors were encountered: