kou commented on PR #50924:
URL: https://github.com/apache/arrow/pull/50924#issuecomment-5362153840

   Hmm. I don't think that this is a right fix.
   
   Upgrading bundled bzip2 is OK but we should use system bzip2 in our CI.
   
   bzip2 is installed by conda:
   
   
https://github.com/apache/arrow/actions/runs/32365959602/job/96416050221?pr=50924#step:6:250
   
   ```text
   bzip2                                         1.0.8               
hda65f42_10             conda-forge
   ```
   
   But we couldn't find it:
   
   
https://github.com/apache/arrow/actions/runs/32365959602/job/96416050221?pr=50924#step:6:572
   
   ```text
   Run-time dependency bzip2 found: NO  (tried pkg-config)
   ```
   
   bzip2 was found before:
   
   
https://github.com/apache/arrow/actions/runs/29545272707/job/87782813509#step:6:572
   
   ```text
   Has header "bzlib.h" : YES 
   Library bz2 found: YES
   ```
   
   Can we use conda bzip2 again?
   
   I think that we should not add `arrow_deps` to `arrow_dep`. We should be 
able to use `libarrow.so` without specifying dependency `.so` explicitly. 
(`-larrow` should work. We should not need `-larrow -lsimdjson ...`.)
   
   These warnings may be related:
   
   
https://github.com/apache/arrow/actions/runs/32355841269/job/96385713260#step:6:6310
   
   ```text
   /opt/conda/envs/arrow/bin/x86_64-conda-linux-gnu-ld: warning: 
libbrotlidec.so.1, needed by src/arrow/libarrow.so, not found (try using -rpath 
or -rpath-link)
   /opt/conda/envs/arrow/bin/x86_64-conda-linux-gnu-ld: warning: 
libbrotlienc.so.1, needed by src/arrow/libarrow.so, not found (try using -rpath 
or -rpath-link)
   /opt/conda/envs/arrow/bin/x86_64-conda-linux-gnu-ld: warning: liblz4.so.1, 
needed by src/arrow/libarrow.so, not found (try using -rpath or -rpath-link)
   /opt/conda/envs/arrow/bin/x86_64-conda-linux-gnu-ld: warning: 
libsnappy.so.1, needed by src/arrow/libarrow.so, not found (try using -rpath or 
-rpath-link)
   /opt/conda/envs/arrow/bin/x86_64-conda-linux-gnu-ld: warning: libz.so.1, 
needed by src/arrow/libarrow.so, not found (try using -rpath or -rpath-link)
   /opt/conda/envs/arrow/bin/x86_64-conda-linux-gnu-ld: warning: libzstd.so.1, 
needed by src/arrow/libarrow.so, not found (try using -rpath or -rpath-link)
   /opt/conda/envs/arrow/bin/x86_64-conda-linux-gnu-ld: warning: 
libazure-core.so.1.16.3, needed by src/arrow/libarrow.so, not found (try using 
-rpath or -rpath-link)
   /opt/conda/envs/arrow/bin/x86_64-conda-linux-gnu-ld: warning: 
libazure-identity.so.1.13.3, needed by src/arrow/libarrow.so, not found (try 
using -rpath or -rpath-link)
   /opt/conda/envs/arrow/bin/x86_64-conda-linux-gnu-ld: warning: 
libazure-storage-blobs.so.12.18.0, needed by src/arrow/libarrow.so, not found 
(try using -rpath or -rpath-link)
   /opt/conda/envs/arrow/bin/x86_64-conda-linux-gnu-ld: warning: 
libazure-storage-files-datalake.so.12.16.0, needed by src/arrow/libarrow.so, 
not found (try using -rpath or -rpath-link)
   /opt/conda/envs/arrow/bin/x86_64-conda-linux-gnu-ld: warning: 
libgoogle_cloud_cpp_common.so.2, needed by src/arrow/libarrow.so, not found 
(try using -rpath or -rpath-link)
   /opt/conda/envs/arrow/bin/x86_64-conda-linux-gnu-ld: warning: 
libabsl_time.so.2401.0.0, needed by src/arrow/libarrow.so, not found (try using 
-rpath or -rpath-link)
   /opt/conda/envs/arrow/bin/x86_64-conda-linux-gnu-ld: warning: 
libabsl_time_zone.so.2401.0.0, needed by src/arrow/libarrow.so, not found (try 
using -rpath or -rpath-link)
   /opt/conda/envs/arrow/bin/x86_64-conda-linux-gnu-ld: warning: 
libgoogle_cloud_cpp_storage.so.2, needed by src/arrow/libarrow.so, not found 
(try using -rpath or -rpath-link)
   /opt/conda/envs/arrow/bin/x86_64-conda-linux-gnu-ld: warning: 
libsimdjson.so.33, needed by src/arrow/libarrow.so, not found (try using -rpath 
or -rpath-link)
   ```
   
   @tadeja may help us if this is related to some conda changes. 
https://github.com/apache/arrow/pull/50903 may be related.


-- 
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]

Reply via email to