[
https://issues.apache.org/jira/browse/ARROW-5871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16880734#comment-16880734
]
Wes McKinney commented on ARROW-5871:
-------------------------------------
Strangely this seems to only be a problem with the Python 3.7 manylinux1 wheel
{code}
(pyarrow-0.14-wheel-3.7) 16:50 ~/code/arrow (ARROW-5863)$ ldd
~/miniconda/envs/pyarrow-0.14-wheel-3.6/lib/python3.6/site-packages/pyarrow/lib.cpython-36m-x86_64-linux-gnu.so
| grep crypt
(pyarrow-0.14-wheel-3.7) 16:50 ~/code/arrow (ARROW-5863)$ ldd
~/miniconda/envs/pyarrow-0.14-wheel-3.7/lib/python3.7/site-packages/pyarrow/lib.cpython-37m-x86_64-linux-gnu.so
| grep crypt
libcrypt.so.1 => /lib/x86_64-linux-gnu/libcrypt.so.1
(0x00007f0e4e392000)
{code}
It seems that we will need to link OpenSSL static libraries as with
https://github.com/apache/arrow/commit/00505b55625ed47d239ca2fb8087bd708097b414
Really I wish we could stop using wheels, it would allow people like me to get
back to building new things instead of debugging this stuff
> [Python] Can't import pyarrow 0.14.0 due to mismatching libcrypt
> ----------------------------------------------------------------
>
> Key: ARROW-5871
> URL: https://issues.apache.org/jira/browse/ARROW-5871
> Project: Apache Arrow
> Issue Type: Bug
> Components: Packaging
> Affects Versions: 0.14.0
> Environment: 5.1.16-300.fc30.x86_64
> Python 3.7.3
> libxcrypt-4.4.6-2.fc30.x86_64
> Reporter: Suvayu Ali
> Priority: Major
> Fix For: 0.14.1
>
>
> In a freshly created virtual environment, after I install pyarrow 0.14.0
> (using pip), importing pyarrow from the python prompt leads to crash:
> {code:java}
> $ mktmpenv
> [..]
> This is a temporary environment. It will be deleted when you run 'deactivate'.
> $ pip install pyarrow
> Collecting pyarrow
> Using cached
> https://files.pythonhosted.org/packages/8f/fa/407667d763c25c3d9977e1d19038df3b4a693f37789c4fe1fe5c74a6bc55/pyarrow-0.14.0-cp37-cp37m-manylinux2010_x86_64.whl
> Collecting numpy>=1.14 (from pyarrow)
> Using cached
> https://files.pythonhosted.org/packages/fc/d1/45be1144b03b6b1e24f9a924f23f66b4ad030d834ad31fb9e5581bd328af/numpy-1.16.4-cp37-cp37m-manylinux1_x86_64.whl
> Collecting six>=1.0.0 (from pyarrow)
> Using cached
> https://files.pythonhosted.org/packages/73/fb/00a976f728d0d1fecfe898238ce23f502a721c0ac0ecfedb80e0d88c64e9/six-1.12.0-py2.py3-none-any.whl
> Installing collected packages: numpy, six, pyarrow
> Successfully installed numpy-1.16.4 pyarrow-0.14.0 six-1.12.0
> $ python --version
> Python 3.7.3
> $ python -m pyarrow
> Traceback (most recent call last):
> File "/usr/lib64/python3.7/runpy.py", line 183, in _run_module_as_main
> mod_name, mod_spec, code = _get_module_details(mod_name, _Error)
> File "/usr/lib64/python3.7/runpy.py", line 142, in _get_module_details
> return _get_module_details(pkg_main_name, error)
> File "/usr/lib64/python3.7/runpy.py", line 109, in _get_module_details
> __import__(pkg_name)
> File
> "/home/user/.virtualenvs/tmp-8a4d52e7bb62853/lib/python3.7/site-packages/pyarrow/__init__.py",
> line 49, in <module>
> from pyarrow.lib import cpu_count, set_cpu_count
> ImportError: libcrypt.so.1: cannot open shared object file: No such file or
> directory{code}
> This is surprising because I have older versions of pyarrow (up to 0.13.0)
> working, and libcrypt on my system (Fedora 30, Python 3.7) is libcrypt.so.2!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
