mirror of
https://github.com/apache/impala.git
synced 2026-01-27 15:03:20 -05:00
On some systems, we have seen the build for the impala-python virtualenv refer to system gcc directly, even though we have specified Impala toolchain's gcc via CC. When the system gcc is newer than Impala's gcc, it fails to execute because it needs symbols that are not present in Impala's libstdc++: gcc: /home/joe/impala/toolchain/toolchain-packages-gcc10.4.0/gcc-10.4.0/lib64/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by gcc) This adds the toolchain gcc to the PATH when building the impala-python virtualenv. This means that any direct reference to gcc will use our compiler rather than system gcc. We continue to have CC pointed to our compiler. Testing: - Ran a build on Redhat 9 where the issue presented Change-Id: Ia5ddd6a88b41a3f8ba04d13538b3de2d9499cbf5 Reviewed-on: http://gerrit.cloudera.org:8080/20114 Reviewed-by: Michael Smith <michael.smith@cloudera.com> Tested-by: Impala Public Jenkins <impala-public-jenkins@cloudera.com>
20 KiB
20 KiB