You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@arrow.apache.org by "Wes McKinney (JIRA)" <ji...@apache.org> on 2019/06/27 16:57:00 UTC
[jira] [Resolved] (ARROW-5751) [Packaging][Python] Python macOS
wheels have dynamic dependency on libcares
[ https://issues.apache.org/jira/browse/ARROW-5751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wes McKinney resolved ARROW-5751.
---------------------------------
Resolution: Fixed
Fix Version/s: 0.14.0
Issue resolved by pull request 4725
[https://github.com/apache/arrow/pull/4725]
> [Packaging][Python] Python macOS wheels have dynamic dependency on libcares
> ---------------------------------------------------------------------------
>
> Key: ARROW-5751
> URL: https://issues.apache.org/jira/browse/ARROW-5751
> Project: Apache Arrow
> Issue Type: Improvement
> Reporter: Philipp Moritz
> Assignee: Wes McKinney
> Priority: Blocker
> Labels: pull-request-available
> Fix For: 0.14.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> I'm afraid while [https://github.com/apache/arrow/pull/4685] fixed the macOS wheels for python 3, but the python 2.7 wheel is still broken (with a different error):
> {code:java}
> ImportError: dlopen(/Users/pcmoritz/anaconda3/lib/python3.6/site-packages/pyarrow/lib.cpython-36m-darwin.so, 2): Library not loaded: /usr/local/opt/c-ares/lib/libcares.2.dylib
> Referenced from: /Users/pcmoritz/anaconda3/lib/python3.6/site-packages/pyarrow/libarrow_python.14.dylib
> Reason: image not found{code}
> I tried the same hack as in [https://github.com/apache/arrow/pull/4685] for libcares but it doesn't work (removing the .dylib fails one of the earlier build steps). I think the only way to go forward on this is to compile grpc ourselves. My attempt to do this in [https://github.com/apache/arrow/compare/master...pcmoritz:mac-wheels-py2] fails because OpenSSL is not found even though I'm specifying the OPENSSL_ROOT_DIR (see [https://travis-ci.org/pcmoritz/crossbow/builds/550603543]). Let me know if you have any ideas how to fix this!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)