You might have to wait for Antoine's help after the holidays. In the meantime: do you get the error when building both with gcc 4.8/4.9 and clang-6.0? I did a bit of google searching and it seems that iostream is a common troublemaker for LLVM. I wonder if the code can be refactored to avoid using std::cout
On Thu, Dec 27, 2018 at 3:56 AM Ravindra Pindikura <ravin...@dremio.com> wrote: > > Thanks Wes, that worked. > > When I run the gandiva tests (I did a step-through with pdb), I get this > error : > > > /home/ravindra/git/arrow/python/pyarrow/tests/test_gandiva.py(50)test_tree_exp_builder() > -> schema, [expr], pa.default_memory_pool()) > (Pdb) > LLVM ERROR: Program used external function '_ZNSt8ios_base4InitC1Ev' which > could not be resolved! > > I had hit the same issue with java/jni, and resolved it by doing a > NativeLibrary.getInstance() (thanks to @pitrou). My knowledge of python is > limited - can someone please help with the same for python ? > > Thanks & regards, > ravindra. > > > On Dec 26, 2018, at 7:55 PM, Wes McKinney <wesmck...@gmail.com> wrote: > > > > hi Ravindra, > > > > If you are using Anaconda, you need to use the conda instructions for > > environment setup instead of virtualenv. This should be called out > > more prominently in a warning in the docs > > > > - Wes > > > > On Tue, Dec 25, 2018 at 12:53 PM Ravindra Pindikura <ravin...@dremio.com> > > wrote: > >> > >> Hi, > >> > >> My change (decimal support in gandiva) causes a CI failure in python > >> test_gandiva.py > >> > >> https://travis-ci.org/apache/arrow/jobs/471874254#L7167 > >> > >> However, the travis log has no further information on the failure. > >> > >> To debug this, I tried setting up a python dev environment on ubuntu 14 > >> using the steps in > >> https://github.com/apache/arrow/blob/master/docs/source/python/development.rst > >> > >> I got stuck at this (virtualenv pyarrow): > >> > >> ValueError: failed to parse CPython sys.version: '3.6.7 |Anaconda, Inc.| > >> (default, Oct 23 2018, 19:19:38) \n[GCC 7.3.0]' > >> > >> > >> Is this a known issue ? Any workaround ? > >> > >> Thanks & regards, > >> Ravindra. > >> > >> >
