pitrou commented on issue #47229: URL: https://github.com/apache/arrow/issues/47229#issuecomment-3221392042
> Instead, rebuild arrow and pyarrow as bellow solved the illegal instruction on both platforms: > > `--build-arg CC="gcc -march=armv8-a -mtune=cortex-a57 -mno-outline-atomics` `--build-arg CXX="g++ -march=armv8-a -mtune=cortex-a57 -mno-outline-atomics ` > > `--build-arg CC="gcc -march=armv8-a -mtune=cortex-a72 -mno-outline-atomics` `--build-arg CXX="g++ -march=armv8-a -mtune=cortex-a72 -mno-outline-atomics` > > > Pass extra flags to arrow/cpp/release > > `-DMI_USE_LIBATOMIC=ON ` > > `-DARROW_MIMALLOC=OFF` > > > Pass extra flags to pyarrow > > `ENV MI_USE_LIBATOMIC=ON` > > `ENV DARROW_MIMALLOC=OFF` Did you need all these flags? Or is it "add options to CC *or* disable mimalloc?" > It seems that both ARMv8.0 variants do not support the pyarrow whell prebuild arch64 version, and so, without knowing your perspective on supporting older CPU versions, I wonder if you intend to support them on https://pypi.org/project/pyarrow/ or it's up to us (consumers) to build it? Well, the question is more: why are these instructions emitted by default, even though we (AFAIR) didn't change anything in our build chain in that regard? @cyb70289 Would you have any idea why this suddenly happens? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
