You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Bankim Bhavsar (Jira)" <ji...@apache.org> on 2020/06/29 21:27:00 UTC

[jira] [Commented] (KUDU-3160) Upgrade devtoolset version for el6

    [ https://issues.apache.org/jira/browse/KUDU-3160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17148150#comment-17148150 ] 

Bankim Bhavsar commented on KUDU-3160:
--------------------------------------

Some findings so far:
1) Tried building kudu (debug) with the latest devtoolset8 on CentOS 6.10

https://www.softwarecollections.org/en/scls/rhscl/devtoolset-8/
Errors were encountered while building python2.7 in thirdparty which is needed for llvm build and perhaps other components as well.
Python version installed on CentOS6.19 system is 2.6.6

{noformat}
ar rc libpython2.7.a Modules/config.o Modules/getpath.o Modules/main.o Modules/gcmodule.o
ar rc libpython2.7.a Modules/threadmodule.o  Modules/signalmodule.o  Modules/posixmodule.o  Modules/errnomodule.o  Modules/pwdmodule.o  Modules/_sre.o  Modules/_codecsmodule.o  Modules/_weakref.o  Modules/zipimport.o  Modules/symtablemodule.o  Modules/xxsubtype.o
ranlib libpython2.7.a
gcc -pthread  -Xlinker -export-dynamic -o python \
		Modules/python.o \
		libpython2.7.a -lpthread -ldl  -lutil   -lm
libpython2.7.a(posixmodule.o): In function `posix_tmpnam':
/root/src/kudu/thirdparty/src/python-2.7.13/Modules/posixmodule.c:7614: warning: the use of `tmpnam_r' is dangerous, better use `mkstemp'
libpython2.7.a(posixmodule.o): In function `posix_tempnam':
/root/src/kudu/thirdparty/src/python-2.7.13/Modules/posixmodule.c:7561: warning: the use of `tempnam' is dangerous, better use `mkstemp'
./python -E -S -m sysconfig --generate-posix-vars ;\
if test $? -ne 0 ; then \
	echo "generate-posix-vars failed" ; \
	rm -f ./pybuilddir.txt ; \
	exit 1 ; \
fi
/bin/sh: line 5: 76967 Segmentation fault      (core dumped) ./python -E -S -m sysconfig --generate-posix-vars
{noformat}

2) Tried building with devtoolset7
https://www.softwarecollections.org/en/scls/rhscl/devtoolset-7/

Hit error linking in thirdparty for what looks like llvm build. llvm build does supply custom PYTHONPATH and but for some reason it's not getting picked up it seems and hits following error.

{noformat}
[ 97%] Linking CXX shared library ../lib/libc++.so
Traceback (most recent call last):
  File "/root/src/kudu/thirdparty/src/llvm-9.0.0.src/projects/libcxx/utils/gen_link_script.py", line 15, in <module>
    import argparse
ImportError: No module named argparse
make[2]: *** [src/CMakeFiles/cxx_shared.dir/build.make:611: lib/libc++.so.1.0] Error 1
make[2]: *** Deleting file 'lib/libc++.so.1.0'
make[1]: *** [CMakeFiles/Makefile2:548: src/CMakeFiles/cxx_shared.dir/all] Error 2
make: *** [Makefile:130: all] Error 2
{noformat}

Next noticed that module {{argparse}} was introduced in python 2.7, so instead enabled python2.7 using following instructions.
http://blog.leifmadsen.com/blog/2017/01/03/installing-python-2.7-on-centos-6.x/

Thereafter thirdparty build and kudu debug build was successful.
Observed following 2 test failures with debug build.
{noformat}
	 11 - client_symbol-test (Failed)
	184 - security-itest (Failed)
{noformat}

For client_symbol-test here is a snippet, will upload the full test file.
{noformat}
	Found bad symbol '_ZGTtNKSt13runtime_error4whatEv'
	Found bad symbol '_ZGTtNSt11logic_errorC1EPKc'
	Found bad symbol '_ZGTtNSt11logic_errorC1ERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE'
	Found bad symbol '_ZGTtNSt11logic_errorC2EPKc'
	Found bad symbol '_ZGTtNSt11logic_errorC2ERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE'
	Found bad symbol '_ZGTtNSt11logic_errorD0Ev'
        ....
        Found bad symbol 'operator delete(void*, unsigned long)'
{noformat}

For security-itest failure
{noformat}
	W0626 17:08:34.175127 521610 init.cc:315] Could not find kerberos principal in credential cache '/tmp/kudutest-0/security-itest.0.SecurityITest.TestCorruptKerberosCC.1593216495267462-521610/krb5kdc/krb5cc' of type FILE
	/root/src/kudu/src/kudu/integration-tests/security-itest.cc:438: Failure
	Failed
	Bad status: Runtime error: Could not find TGT in cache after kinit
	Google Test trace:
	/root/src/kudu/src/kudu/integration-tests/security-itest.cc:422: Truncating ccache at '/tmp/kudutest-0/security-itest.0.SecurityITest.TestCorruptKerberosCC.1593216495267462-521610/krb5kdc/krb5cc' to 206
{noformat}

> Upgrade devtoolset version for el6
> ----------------------------------
>
>                 Key: KUDU-3160
>                 URL: https://issues.apache.org/jira/browse/KUDU-3160
>             Project: Kudu
>          Issue Type: Task
>          Components: build
>    Affects Versions: 1.12.0
>            Reporter: Bankim Bhavsar
>            Priority: Major
>
> Currently for building RHEL6 based distributions, kudu uses devtoolset3.
> However devtoolset3 is EOL as of Nov 2016 and it's repo location has been removed from the official software collections repository. See related KUDU-3159.
> So upgrade devtoolset to a newer version for building kudu on RHEL6 based distributions.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)