[ https://issues.apache.org/jira/browse/IMPALA-3926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tim Armstrong reassigned IMPALA-3926: ------------------------------------- Assignee: Tim Armstrong > Reconsider use of LD_LIBRARY_PATH for toolchain libraries > --------------------------------------------------------- > > Key: IMPALA-3926 > URL: https://issues.apache.org/jira/browse/IMPALA-3926 > Project: IMPALA > Issue Type: Improvement > Components: Infrastructure > Affects Versions: Impala 2.6.0 > Reporter: Matthew Jacobs > Assignee: Tim Armstrong > Priority: Major > Labels: build, toolchain > > Right now, impala-config.sh puts a lot of libraries in LD_LIBRARY_PATH, but > this can be a problem for binaries that aren't from our builds or explicitly > built against these specific libraries. One solution is to move any tools we > need into the toolchain and build against these libraries. While this may be > a reasonable thing to do (i.e. moving all tools we need into the toolchain), > we should consider if setting LD_LIBRARY_PATH for the whole Impala > environment is really necessary and the right thing to do (e.g. [some people > say using LD_LIBRARY_PATH is > bad|http://xahlee.info/UnixResource_dir/_/ldpath.html]). -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org