[
https://issues.apache.org/jira/browse/ARROW-3860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16697453#comment-16697453
]
Wes McKinney commented on ARROW-3860:
-------------------------------------
Sorry, it wasn't clear to me that the packaging you were describing is part of
the repository. In part this is because the community does not have regular
visibility into these packaging jobs and whether they work or not. I'd love to
be able to easily run all of the tasks as part of verifying changes to the
build system. You might want to add some checks to
https://github.com/apache/arrow/blob/master/dev/tasks/gandiva-jars/build-cpp.sh
to assert that the shared libraries do not have a runtime dependency on
libstdc++
I consider hard-coding {{-static-libstdc++}} in a C++ build system to be a bug,
see ARROW-3437. Also, these packages are not fully portable because they have a
minimum glibc ABI requirement equal to the version in Ubuntu 14.04.
> [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)
