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 "ASF subversion and git services (Jira)" <ji...@apache.org> on 2023/06/24 04:44:00 UTC
[jira] [Commented] (IMPALA-12240) On Redhat 9, Impala fails to build the impala-python virtualenv
[ https://issues.apache.org/jira/browse/IMPALA-12240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17736664#comment-17736664 ]
ASF subversion and git services commented on IMPALA-12240:
----------------------------------------------------------
Commit 7b502f7c965fe9236b034b2ef0ec86d9055c3901 in impala's branch refs/heads/master from Joe McDonnell
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=7b502f7c9 ]
IMPALA-12240: Put gcc on the PATH when building the impala-python venv
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 <mi...@cloudera.com>
Tested-by: Impala Public Jenkins <im...@cloudera.com>
> On Redhat 9, Impala fails to build the impala-python virtualenv
> ---------------------------------------------------------------
>
> Key: IMPALA-12240
> URL: https://issues.apache.org/jira/browse/IMPALA-12240
> Project: IMPALA
> Issue Type: Bug
> Components: Infrastructure
> Affects Versions: Impala 4.3.0
> Reporter: Joe McDonnell
> Assignee: Joe McDonnell
> Priority: Blocker
>
> On Redhat 9, bootstrapping the impala-python virtualenv seems to call system gcc directly rather than using the CC environment variable. Because system GCC is newer than Impala's toolchain gcc, it fails to execute because it needs symbols that are not in Impala toolchain's libstdc++:
> {noformat}
> gcc -shared -L/mnt/build/bzip2-1.0.8-p2/lib -L/mnt/build/bzip2-1.0.8-p2/lib build/temp.linux-x86_64-3.7/src/base64.o build/temp.linux-x86_64-3.7/src/kerberos.o build/temp.linux-x86_64-3.7/src/kerberosbasic.o build/temp.linux-x86_64-3.7/src/kerberosgss.o build/temp.linux-x86_64-3.7/src/kerberospw.o -o build/lib.linux-x86_64-3.7/kerberos.cpython-37m-x86_64-linux-gnu.so -Wl,-z,relro -Wl,--as-needed -Wl,-z,now -lgssapi_krb5 -lkrb5 -lk5crypto -lcom_err
> 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)
> {noformat}
> It's unclear why there is a direct call to system gcc. Oddly, this does not reproduce on Rocky 9.2.
> Probably the simplest solution is for bootstrap_virtualenv.py to add gcc's bin directory to the PATH so that any direct calls use our gcc/g++.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org