You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues-all@impala.apache.org by "Todd Lipcon (JIRA)" <ji...@apache.org> on 2018/05/24 00:48:00 UTC

[jira] [Commented] (IMPALA-7066) Provide option to build impalad with native-toolchain dependencies linked statically

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

Todd Lipcon commented on IMPALA-7066:
-------------------------------------

The difficulty with libkudu_client specifically is that it has some symbols which overlap names with symbols in Impala. With a shared object we are able to make those symbols local so they don't conflict, but with a static library that isn't an option. We'd need to do something more clever involving renaming the conflicting symbols within the shared object.

> Provide option to build impalad with native-toolchain dependencies linked statically
> ------------------------------------------------------------------------------------
>
>                 Key: IMPALA-7066
>                 URL: https://issues.apache.org/jira/browse/IMPALA-7066
>             Project: IMPALA
>          Issue Type: New Feature
>          Components: Infrastructure
>            Reporter: Quanlong Huang
>            Priority: Major
>
> Users can be stuck into issues in upgrading Impala if they just replace the impalad binary and jars but forget (or are unaware) to replace the dependent libraries like libkudu_client, libstdc++, libgcc etc.
> It'd be better if we have a build option to link them statically.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org