[ 
https://issues.apache.org/jira/browse/ARROW-3860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16697833#comment-16697833
 ] 

Praveen Kumar Desabandu commented on ARROW-3860:
------------------------------------------------

Thanks a lot Wes. Agreed on all points.
 # I will fix the crossbow build file and add some check to the crossbow file 
to check the shared libs do not have a runtime dependency on std-c++.
 # Yes we will have a dependency on glibc version of Ubuntu, but the most 
common versions installed at the customer base seems to be CentOS 7+ and they 
are good with this minimum version of glibc. We have pending work to support 
CentOS6 like environments which have a lower version of glibc.
 # Also when i change the crossbow script it will affect the arrow packaging of 
gandiva (since the shared libs with statically link to std c++) . Would it be 
ok to use the same for arrow distribution (or) should i make this dynamic so 
that arrow/crossbow still builds gandiva with dynamic dependency on std-c++ 
while other clients can customize as per their need?

> [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)

Reply via email to