You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@graphar.apache.org by "adsharma (via GitHub)" <gi...@apache.org> on 2026/03/15 00:22:51 UTC

Re: [I] feat(python): Link against PyArrow arrow libraries to resolve manylinux limitations [incubator-graphar]

adsharma commented on issue #836:
URL: https://github.com/apache/incubator-graphar/issues/836#issuecomment-4061788202

   Bump. Any progress on this?
   
   I've run into this issue twice now:
   
   * Conflict between `icebug` and `pyarrow` on `libarrow.so` version (link in previous comment)
   * Conflict between `icebug` and `pytorch` on `libomp.so/dylib` version (https://github.com/Ladybug-Memory/icebug/pull/21)
   
   Both were resolved by excluding the offending library from icebug and using the more widely distributed pyarrow/pytorch versions.
   
   My general sense is that it's catastrophic to distribute two incompatible versions of the library. It'll immediately result in an end user visible crash. Tracking the widely distributed shared library and compiling against the nearest feasible version of that library is the less harmful of the two solutions.
   
   My observation is that `libarrow` and `libomp` avoid ABI incompatible changes within a major version. So even if you compile against a slightly different version of headers you'll be ok.
   
   I hope you ship something end users can use very soon!


-- 
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: commits-unsubscribe@graphar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@graphar.apache.org
For additional commands, e-mail: commits-help@graphar.apache.org