[
https://issues.apache.org/jira/browse/ARROW-5751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16874158#comment-16874158
]
Wes McKinney commented on ARROW-5751:
-------------------------------------
You're right, forgot about that.
Also the output is weird:
{code}
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}
This says Python 3.6, did you actually get the error on py2.7 or py3.6?
> [Packaging][Python] Python 2.7 wheels broken on macOS: libcares.2.dylib not
> found
> ---------------------------------------------------------------------------------
>
> Key: ARROW-5751
> URL: https://issues.apache.org/jira/browse/ARROW-5751
> Project: Apache Arrow
> Issue Type: Improvement
> Reporter: Philipp Moritz
> Priority: Blocker
>
> 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)
