Re: Building against arrow static library

2018-06-26 Thread Wes McKinney
See note about this in https://github.com/apache/arrow/blob/master/python/doc/source/development.rst#known-issues On Tue, Jun 26, 2018 at 7:10 AM, Wes McKinney wrote: > Ah, ok, I think I know the issue then. You need to pass > -DCMAKE_CXX_FLAGS='-D_GLIBCXX_USE_CXX11_ABI=0' when building all your

Re: Building against arrow static library

2018-06-26 Thread Wes McKinney
Ah, ok, I think I know the issue then. You need to pass -DCMAKE_CXX_FLAGS='-D_GLIBCXX_USE_CXX11_ABI=0' when building all your libraries if you use the conda-forge libraries, since they are built using the old gcc ABI On Tue, Jun 26, 2018 at 5:11 AM, Praveen Kumar wrote: > Hi Wes, > > Thanks for t

Re: Building against arrow static library

2018-06-26 Thread Praveen Kumar
Hi Wes, Thanks for the suggestion. I purged the system boost libs and removed LLVM (suspecting it might be bringing in some static dependencies) too. Then recompiled Arrow and tried to link Gandiva again but no avail. It looks similar to the one seen here, https://issues.apache.org/jira/browse/AR

Re: Building against arrow static library

2018-06-25 Thread Wes McKinney
hi Praveen, Are /usr/include or /usr/local/include getting added to your build paths (this could happen if you have LLVM or some other library in your system paths)? Unfortunately, when you're using conda libraries or an external toolchain at all, you have to be really strict about toolchain isol

Re: Building against arrow static library

2018-06-25 Thread Praveen Kumar
Tried that did not help. I also tried to link in the boost libraries myself since it was not clear if arrow was including the transitive dependencies from the build script. That does not help as well. On Mon, Jun 25, 2018 at 7:55 PM, Dimitri Vorona < alen...@googlemail.com.invalid> wrote: > Hi,

Re: Building against arrow static library

2018-06-25 Thread Dimitri Vorona
Hi, I'd this a similar issue some time ago, and the solution was building after a clean checkout, which I interpreted as some kind of caching issue. Generally, I've found that starting with a clean checkout and following the steps from [0] never failed for me. Hope that helps! Cheers, Dimitri.