Then instead pass "-D_GLIBCXX_USE_CXX11_ABI=0" when building the C++
libraries?
Le 10/10/2022 à 20:20, Joseph Porter a écrit :
Hi Antoine,
Here's what I did:
export PYARROW_CXXFLAGS="-std=c++11 -D_GLIBCXX_USE_CXX11_ABI=1"
Here's what I got:
ImportError:
/workspace/arrow/pyarrow-test/lib/python3.8/site-packages/pyarrow/
lib.cpython-38-x86_64-linux-gnu.so: undefined symbol:
_ZNK5arrow8DataType18ComputeFingerprintEv
It looks like the symbol mismatch exists already in the libraries that were
created by the C++ build step, which is why I tried to add the c++11
directives to the CMakeLists.txt in the python module.
-Joe
On Mon, Oct 10, 2022 at 12:37 PM Antoine Pitrou <anto...@python.org> wrote:
Le 10/10/2022 à 19:27, Joseph Porter a écrit :
I've tried building with explicit flags to encourage the libraries to
include the cxx11 symbol (in python/CMakeLists.txt). That doesn't seem
to
impact this issue:
set (CMAKE_CXX_STANDARD 11)
set (CMAKE_CXX_STANDARD_REQUIRED ON)
set (CMAKE_CXX_EXTENSIONS OFF)
I also added
export PYARROW_CXXFLAGS="-std=c++11"
for the wheel build of pyarrow (no effect).
Can you try adding "-D_GLIBCXX_USE_CXX11_ABI=1" to those flags?