Thanks for clearing that up Wes! I couldn't figure out why it was working before I updated, but makes sense now. I'd be happy to add this to the Python README, is it worth opening a JIRA for it?
Bryan On Wed, Nov 2, 2016 at 1:09 PM, Wes McKinney <[email protected]> wrote: > libarrow.so needs to be in your LD_LIBRARY_PATH while you are developing, > i.e. > > export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$ARROW_HOME/lib > > Might be a good idea to add this to the README > > We used to have SET(CMAKE_INSTALL_RPATH_USE_LINK_PATH TRUE), but this > hard-codes the location of the linked library in the pyarrow shared > libraries' rpaths. By leaving it to LD_LIBRARY_PATH you can easily > switch between debug and release builds of libarrow, for example. > > - Wes > > On Wed, Nov 2, 2016 at 2:18 PM, Bryan Cutler <[email protected]> wrote: > > After building pyarrow, running py.tests or trying to "import pyarrow" > > results in the error: > > > > /usr/lib/python2.7/dist-packages/py/_path/local.py:650: in pyimport > > __import__(modname) > > pyarrow/__init__.py:20: in <module> > > import pyarrow.config > > E ImportError: libarrow.so: cannot open shared object file: No such > file > > or directory > > > > I have this and the other shared libs under my ARROW_HOME, and had the > env > > var exported through the build process. If I just copy the *.so files > > alongside libpyarrow.so, everything works fine. I'm not sure how it is > > supposed to work here, should the command "python setup.py build_ext > > --inplace" copy these libraries to pyarrow, or should it somehow know to > > look in ARROW_HOME for these? > > > > Thanks! > > Bryan >
