[
https://issues.apache.org/jira/browse/ARROW-3860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16699177#comment-16699177
]
Wes McKinney commented on ARROW-3860:
-------------------------------------
Do you want to just add a temporary build option to enable the behavior that
was hard-coded before? That seems the simplest thing to unblock yourself.
I strongly recommend that you migrate to use Redhat's devtoolset compiler
toolchain so this is not necessary. Using -static-libstdc++ in shared libraries
is a dangerous business; sometimes it will work, other times it won't. It is
best used for producing dependency-free executables
> [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: 1h 20m
> 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)
