AlenkaF commented on issue #55467:
URL: https://github.com/apache/arrow/issues/55467#issuecomment-6763535911
Thank you for the report!
I have installed miniforge on my arm64 macOS (M1), created 3 separate envs
with pyarrow 25.0.1, 26.0.0 and 26.0.1. and found discrepancies on how pyarrow
is linked to lz4 via `otool`. Note I was not able to reproduce the failure
because I have Homebrew's lz4 installed at that path.
Using these commands
```
mamba create -n pa-25-0-1 python=3.15 pyarrow=25.0.1
mamba run -n pa-25-0-1 python -c "import pyarrow"
prefix=~/miniforge3/envs/pa-25-0-1
echo "== pa-25-0-1"; otool -L $prefix/lib/libarrow.*.dylib | grep lz4
```
(and for pa-26-0-0, pa-26-0-1 respectively) I was able to get:
**pyarrow=25.0.1**
Linking lz4-c-1.10.0-hdca3b7d_2 (when creating the env)
```
== pa-25-0-1
@rpath/liblz4.1.dylib (compatibility version 1.0.0, current version
1.10.0)
@rpath/liblz4.1.dylib (compatibility version 1.0.0, current version
1.10.0)
```
**pyarrow=26.0.0**
Linking lz4-c-1.10.0-hdca3b7d_2 (when creating the env)
```
== pa-26-0-0
@rpath/liblz4.1.dylib (compatibility version 1.0.0, current version
1.10.0)
@rpath/liblz4.1.dylib (compatibility version 1.0.0, current version
1.10.0)
```
**pyarrow=26.0.1**
Linking lz4-c-1.10.0-hdca3b7d_2 (when creating the env)
```
== pa-26-0-1
/opt/homebrew/opt/lz4/lib/liblz4.1.dylib (compatibility version
1.0.0, current version 1.10.0)
/opt/homebrew/opt/lz4/lib/liblz4.1.dylib (compatibility version
1.0.0, current version 1.10.0)
```
In the last run the link is set to `/opt/homebrew/opt/lz4/` instead of
`@rpath/liblz4.1.dylib`. I think this belongs to conda-forge,, cc @raulcd
--
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]
