You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@arrow.apache.org by "Uwe L. Korn (JIRA)" <ji...@apache.org> on 2017/05/06 19:46:04 UTC
[jira] [Commented] (ARROW-909) libjemalloc.so.2: cannot open shared
object file:
[ https://issues.apache.org/jira/browse/ARROW-909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15999551#comment-15999551 ]
Uwe L. Korn commented on ARROW-909:
-----------------------------------
[~abdulrahman004] Did you have any special compilation/linking options set? Normally {{pyarrow/_config.so}} should not link to {{libjemalloc.so.2}}. If you are able to run {{lddtree pyarrow/_config.so}}, it would really help me to understand where the linkage is coming from.
I made PR https://github.com/apache/arrow/pull/651 to cover for the initial problem that when building jemalloc as an external project it should be statically linked as the shared library is not installed on {{make install}}.
> libjemalloc.so.2: cannot open shared object file:
> --------------------------------------------------
>
> Key: ARROW-909
> URL: https://issues.apache.org/jira/browse/ARROW-909
> Project: Apache Arrow
> Issue Type: Bug
> Environment: linux centos
> Reporter: Abdul Rahman
> Labels: pyarrow
>
> >>> import pyarrow
> Traceback (most recent call last):
> File "<stdin>", line 1, in <module>
> File "/home/default/src/venv/lib/python2.7/site-packages/pyarrow-0.2.1.dev244+g14bec24-py2.7-linux-x86_64.egg/pyarrow/__init__.py", line 28, in <module>
> import pyarrow._config
> ImportError: libjemalloc.so.2: cannot open shared object file: No such file or directory
> $LD_LIBRARY_PATH has libarrow_jemalloc.a along with other libraries including libarrow.so, libparquet.so, libparquet_arrow.so. Pyarrow was built using ----with-jemalloc and parquet-cpp was cmake-d with
> -DPARQUET_ARROW=ON
> Also, noticed that arrow/python documentation has been cleaned up with the installation instructions having the coda approach only .Is this the only supported way going forward ?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)