I think I found a culprit in the pyarrow cmake config:
if(PYARROW_USE_TENSORFLOW)
# TensorFlow uses the old GLIBCXX ABI, so we have to use it too
set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -D_GLIBCXX_USE_CXX11_ABI=0")
endif()
This was overriding my attempts to add c++11 to the pyarrow build
Hi Andy,
Could you add "adding a release to
https://reporter.apache.org/addrelease.html?arrow " to
release process of DataFusion and Ballista?
The release information is used to generate a template for
a board report.
FYI:
* Board Report Wizard: https://reporter.apache.org/wizard/?arrow
* A
With 9 +1 (4 binding) the release is approved.
The release is available here:
https://dist.apache.org/repos/dist/release/arrow/arrow-object-store-rs-0.5.1
I have also released it to crates.io:
https://crates.io/crates/object_store/0.5.1
Thank you all for voting and reviewing the release
That makes sense. I'll give it a try - thanks!
On Mon, Oct 10, 2022 at 2:34 PM Antoine Pitrou wrote:
>
>
> Le 10/10/2022 à 21:31, Joseph Porter a écrit :
> > No go. I still get the B5cxx11 extension on the symbols in the compiled
> > libarrow library.
>
> "-D_GLIBCXX_USE_CXX11_ABI=0" is a C++
Le 10/10/2022 à 21:31, Joseph Porter a écrit :
No go. I still get the B5cxx11 extension on the symbols in the compiled
libarrow library.
"-D_GLIBCXX_USE_CXX11_ABI=0" is a C++ compiler flag, not a CMake flag.
One possibility is to pass instead
"-DCMAKE_CXX_FLAGS=-D_GLIBCXX_USE_CXX11_ABI=0"
No go. I still get the B5cxx11 extension on the symbols in the compiled
libarrow library.
Tried:
/workspace/arrow/pyarrow-dev/bin/cmake -DCMAKE_INSTALL_PREFIX=$ARROW_HOME
-DCMAKE_INSTALL_LIBDIR=lib -DCMAKE_BUILD_TYPE=Release -DARROW_DATASET=ON
-DARROW_WITH_BZ2=ON -DARROW_WITH_ZLIB=ON
I don't see the point of having two different syntaxes.
Also, IMHO lisp-style is harder for many people, so I would rather a
more "traditional" syntax (though Lisp is historically traditional, of
course ;-)).
Le 10/10/2022 à 21:10, Sasha Krassovsky a écrit :
Yes that makes a lot of
Yes that makes a lot of sense! I’d agree that it would probably be fine to have
two different syntaxes, seeing as the use-cases are a bit different.
Did anyone else have any thoughts? Either on the lisp-style syntax for Arrow’s
Expressions or on having two different syntaxes? (Weston or
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:
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
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
If this isn't the right place to ask, please let me know where to direct
this question:
I'm trying to build a slightly modified version of the 9.0.0 tag for arrow
(particularly Pyarrow). Walking through the build steps (below), I have
run into a problem where the arrow c++ library has symbols
With 9 +1 votes (4 binding), the vote passes. I have published artifacts to
crates.io
Thank you for helping with verifying the release.
On Sat, Oct 8, 2022 at 8:51 PM Kun Liu wrote:
> +1 (non-binding)
>
> Do the validation on Intel Mac
>
> Ashish 于2022年10月9日周日 00:22写道：
>
> > +1 (non-binding)
We've discussed this in the past, I think. In addition to having many
optional components enabled, the pyarrow wheel also includes the unit
tests directory which is of growing size. I think if we made a
pyarrow-slim wheel with support only for core Arrow (IPC, etc.) and
Parquet file reading, it
My vote: +1
The vote passes with 4 binding +1 votes, 8 non-binding +1 votes, and no -1
votes. Thanks all!
I will update the RFC PR and merge it next, and will continue setting up the CI
and release process.
-David
On Wed, Oct 5, 2022, at 15:38, David Li wrote:
> Kirill (CC'd) mentioned the
15 matches
Mail list logo
