[
https://issues.apache.org/jira/browse/ARROW-3860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16698289#comment-16698289
]
Wes McKinney commented on ARROW-3860:
-------------------------------------
It isn't appropriate to statically link libstdc++ in general binary library
distributions -- that's part of why I've been making a stink about this issue
because the binaries produced by this can only be used in a very narrow
context.
If you use the libraries to build an application, depending on the platform
where you build, you may have symbol conflicts that will yield segfaults / core
dumps.
I can see the argument for building the binaries this way in a JAR distribution
of the JNI bindings. Though, beware: if someone links to another JNI-wrapped
C++ library with different symbols, it may crash.
> [Gandiva] [C++] Fix packaging broken recently
> ---------------------------------------------
>
> Key: ARROW-3860
> URL: https://issues.apache.org/jira/browse/ARROW-3860
> Project: Apache Arrow
> Issue Type: Task
> Reporter: Praveen Kumar Desabandu
> Assignee: Praveen Kumar Desabandu
> Priority: Major
> Labels: pull-request-available
> Fix For: 0.12.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> This
> [commit|https://github.com/apache/arrow/commit/ba2b2ea2301f067cc95306e11546ddb6d402a55c#diff-d5e5df5984ba660e999a7c657039f6af]
> broke gandiva packaging by removing static linking of std c++, since dremio
> consumes a fat jar that includes packaged gandiva native libraries we would
> need to statically link std c++
> As suggested in the commit message will re-introduce it as a CMake Flag.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
