[
https://issues.apache.org/jira/browse/ARROW-3860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Praveen Kumar Desabandu reopened ARROW-3860:
--------------------------------------------
Assignee: Praveen Kumar Desabandu (was: Wes McKinney)
In which case the fix would be in
[https://github.com/apache/arrow/blob/master/dev/tasks/gandiva-jars/build-cpp.sh]
So keep the issue open until i fix it?
Also (i am new to the open source development workflow, so please correct me if
i am wrong), Is it not incorrect to add a backward incompatible change that
might break existing behavior? and our priority in that case should be parity
first and then modifying it in an backward compatible manner?
> [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)
