You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Joe McDonnell (Jira)" <ji...@apache.org> on 2020/06/17 02:34:00 UTC
[jira] [Created] (IMPALA-9863) Print warning when developer sets
LD_LIBRARY_PATH with the system library
Joe McDonnell created IMPALA-9863:
-------------------------------------
Summary: Print warning when developer sets LD_LIBRARY_PATH with the system library
Key: IMPALA-9863
URL: https://issues.apache.org/jira/browse/IMPALA-9863
Project: IMPALA
Issue Type: Bug
Components: Infrastructure
Affects Versions: Impala 4.0
Reporter: Joe McDonnell
With the upgrade to GCC 7.5.0, the libstdc++ used for Impala development is now newer than the system libraries on several supported platforms (Centos 7, Ubuntu 16). Ubuntu 16 is particularly important as the main development platform.
Up until recently, bin/bootstrap_system.sh added this line to bin/impala-config-local.sh:
{noformat}
export LD_LIBRARY_PATH=/usr/lib/x86_64-linux-gnu/${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH}{noformat}
This line causes problems for Kudu startup, because Kudu uses symbols from GCC 7.5.0's libstdc++ that are not present in the system libstdc++. When it tries to lookup those symbols, it tries LD_LIBRARY_PATH first and fails with this message:
{noformat}
/opt/Impala-Toolchain/toolchain-packages-gcc7.5.0/kudu-d652cab17/release/bin/kudu-tserver: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.22' not found (required by /opt/Impala-Toolchain/toolchain-packages-gcc7.5.0/kudu-d652cab17/release/bin/kudu-tserver){noformat}
Without the LD_LIBRARY_PATH, the kudu binary would use its RPATH to find the toolchain's libstdc++ (and thus not have this problem).
Let's print a warning for this.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)