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 "Tianyi Wang (JIRA)" <ji...@apache.org> on 2018/05/24 01:16:00 UTC
[jira] [Comment Edited] (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=16488275#comment-16488275 ]
Tianyi Wang edited comment on IMPALA-7066 at 5/24/18 1:15 AM:
--------------------------------------------------------------
Another way to solve the dynamic linking problem is to get "make install" in impala - the dependency would be clearer and the deployment would be as easy as an rsync, without the need of further packaging effort.
was (Author: tianyiwang):
Another way to solve the dynamic linking problem is to get "make install" in impala - the dependency would be clearer and the deployment would be easier.
> 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