-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
PowerPC pip package is not suitable for systems with 64 KiB pages #10073
Comments
I think this is the same root cause as #3791 (comment) The difference is that you're building from source. So you would have to set the env variable yourself as far as I understand. @konstin or is there a way for us to set an env variable in the wheel code? |
I didn't mean to be building from source. I see that the log I attached above was the second time through so
|
maturin doesn't support this atm, but it should be passed through if you set it outside the build command. |
I'm not sure if this is the right place; if not, please point me in the right direction and sorry for the noise.
Trying to run the
pip
packagedruff
on Debian 12.2 on a PowerPC LE system (in Docker, on a Raptor Computing Talos II workstation, if it matters) whoseuname -a
describes itself asLinux 0abaa1dc35a7 6.1.0-13-powerpc64le #1 SMP Debian 6.1.55-1 (2023-09-29) ppc64le GNU/Linux
results in a very short trip:Debian builds their PowerPC kernels to use 64 KiB pages;
/boot/config-$(uname -r)
containsI suspect thatconfiguringjemalloc
to assume 64 KiB pages will allow it to also function on 4 KiB page systems: jemalloc/jemalloc#2572 (comment)The text was updated successfully, but these errors were encountered: