CCS 6.2.0.00048 can't be used on CentOS 6.8 64-bit due to requiring GLIBC_2.14

Chester Gillon

Tried installing CCS 6.2.0.00048 on a CentOS 6.8 64-bit system in which had been previously running CCS 6.1.3.

The CCS 6.2.0 installer first reported a problem about a missing dependency for libpython2.7.so.1.0

As CentOS 6.8 has Python 2.6.6 installed, rather than trying to upgrade the Python version which may break something else, compiled libpython2.7.so.1.0 from the Python 2.7.6 source and manually copied the libpython2.7.so.1.0 to /usr/lib64. That allowed the CCS 6.2.0 install to complete without warnings about missing system libraries.

CCS 6.2.0 could startup and a new project was created. However, attempting to perform a build reported an error due to gmake not finding the required GLIBC_2.14:

**** Build of configuration Debug for project 66AK2H12_typical ****

/home/Mr_Halfword/ti/ccs620/ccsv6/utils/bin/gmake -k all 
/home/Mr_Halfword/ti/ccs620/ccsv6/utils/bin/gmake: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /home/Mr_Halfword/ti/ccs620/ccsv6/utils/bin/gmake)

**** Build Finished ****

CentOS 6.8 uses GLIBC_2.12. It is not possible to update the installed GLIBC version without breaking the system, which means I need to update to a newer Linux version.

However, neither the Release Notes for Code Composer Studio™ v6.2.0 or Linux Host Support CCSv6 Wiki page mention the minimum GLIBC version required by CCS 6.2.0. Could the Release Notes and/or Linux Host Support be updated with the minimum GLIBC version required?

Any maybe the Linux installer could be updated to add a check on the GLIBC version installed?

over 9 years ago

0 desouza over 9 years ago

TI__Guru**** 171104 points

Chester,

Thanks for reporting this. As we only do testing and validation using Ubuntu, in my evaluations I was not able to find any problems with libpython2.7.so.1.0 on versions 14.04 and 16.04.

Regarding the glibc dependency, given that gmake is the only one complaining about it you can simply replace it with a previous version under <CCS_INSTALL_DIR>/ccsv6/utils/bin/

I suspect you have already done so, but I just wanted to check.

One last detail: the Linux 64-bit versions of the TI compilers are not ready yet, therefore the new CCS still depends on a single 32-bit dependency: libc6:i386

Details are at: processors.wiki.ti.com/.../Linux_Host_Support_CCSv6

I am investigating the two suggestions you sent.

Regards,
Rafael

0 desouza over 9 years ago in reply to desouza

TI__Guru**** 171104 points

Chester,

I was informed by the dev team they actually have a script that checks the component versions before the install, but somehow this may not be working for CentOS. I will see if we can publish a manifest of the dependencies before the release.

Regards,
Rafael

0 Chester Gillon over 9 years ago in reply to desouza

Guru 92251 points

desouza said:
Regarding the glibc dependency, given that gmake is the only one complaining about it you can simply replace it with a previous version under <CCS_INSTALL_DIR>/ccsv6/utils/bin/

I suspect you have already done so, but I just wanted to check.

To be honest, once I saw glibc dependency problem with gmake I stopped investigating using CCS 6.2.0 with the CentOS 6.8 system (and moved to using CCS 6.2.0 on Windows). i.e. didn't check if there are any other programs in CCS 6.2.0 with a glibc dependency problem on CentOS 6.8..

Will try CCS 6.2.0 under Linux again once have updated the operating system.

desouza said:
One last detail: the Linux 64-bit versions of the TI compilers are not ready yet, therefore the new CCS still depends on a single 32-bit dependency: libc6:i386

Thanks, I see you updated the WIki today.

desouza said:
I was informed by the dev team they actually have a script that checks the component versions before the install, but somehow this may not be working for CentOS.

Is that similar to the check_depends.sh script which was from the CCS5 Checking Linux Dependencies for CCS?

0 desouza over 9 years ago in reply to Chester Gillon

TI__Guru**** 171104 points

Chester Gillon said:
Is that similar to the check_depends.sh script which was from the CCS5 Checking Linux Dependencies for CCS?

Probably. I don't have access to the installer source code.

0 danishinnis over 9 years ago in reply to desouza

TI__Mastermind 22060 points

Hi Chester,
Could you confirm which version of linux you were installing - the 32 bit or the 64 bit? Could you zip up and post the contents of the install_logs folder?
Thanks
Danish

0 Chester Gillon over 9 years ago in reply to danishinnis

Guru 92251 points

Tried installing CCS 6.2.0.00048 on a CentOS 6.8 64-bit system in which had been previously running CCS 6.1.3.

danishinnis said:
Could you confirm which version of linux you were installing - the 32 bit or the 64 bit?

I was attempting to install the 64-bit CCS 6.2.0.00048 onto a Linux CentOS 6.8 64-bit system.

danishinnis said:
Could you zip up and post the contents of the install_logs folder?

I will do that when next get access to the PC, which won't be until the weekend.

0 Chester Gillon over 9 years ago in reply to danishinnis

Guru 92251 points

danishinnis said:
Could you zip up and post the contents of the install_logs folder?

Attached is the install_logs directory from a CCS 6.2.0.00048 installation on CentOS 6.8 64-bit. 6457.install_logs.zip

During the installation there were no warnings displayed by the install GUI about missing dependent libraries.

From a quick look at the install logs, in the install_logs/20160917100138/ccs_setup_6.2.0.00048_install.log file there are the following messages about a more recent version of GLIBC being needed to run CCS:

09/17/2016 09:01:43(GMT) - Validation::linuxLibChecks - LD_LIBRARY_PATH == :/tmp/ccs_fe1aa7be-3c2e-4059-5d9a-531d548cb6e4/tcl/lib
09/17/2016 09:01:43(GMT) - Validation::linuxLibChecks - tempLD == {}
09/17/2016 09:01:43(GMT) - Validation::linuxLibChecks - cmd = /tmp/ccs_fe1aa7be-3c2e-4059-5d9a-531d548cb6e4/dependency-checker/ldcheck
09/17/2016 09:01:43(GMT) - Validation::linuxLibChecks - ran /tmp/ccs_fe1aa7be-3c2e-4059-5d9a-531d548cb6e4/dependency-checker/ldcheck:
09/17/2016 09:01:43(GMT) - Validation::linuxLibChecks - cmd = /tmp/ccs_fe1aa7be-3c2e-4059-5d9a-531d548cb6e4/dependency-checker/check_depends.sh --ldpath 
09/17/2016 09:01:43(GMT) - Validation::linuxLibChecks - ran /tmp/ccs_fe1aa7be-3c2e-4059-5d9a-531d548cb6e4/dependency-checker/check_depends.sh --ldpath :Installed versions of glibc and glibcxx: GLIBC_2.12, N/A
Required versions of glibc and glibcxx:  GLIBC_2.15, GLIBCXX_3.4.19
WARNING: A more recent GLIBC version is needed to run CCS.
Checking availability of libraries in ext-depends.txt ...
libstdc++ update required.
Done.
09/17/2016 09:01:43(GMT) - Validation::linuxLibChecks - Line: Installed versions of glibc and glibcxx: GLIBC_2.12, N/A
09/17/2016 09:01:43(GMT) - Validation::linuxLibChecks - Line: Required versions of glibc and glibcxx:  GLIBC_2.15, GLIBCXX_3.4.19
09/17/2016 09:01:43(GMT) - Validation::linuxLibChecks - Line: WARNING: A more recent GLIBC version is needed to run CCS.
09/17/2016 09:01:43(GMT) - Validation::linuxLibChecks - Line: Checking availability of libraries in ext-depends.txt ...
09/17/2016 09:01:43(GMT) - Validation::linuxLibChecks - Line: libstdc++ update required.
09/17/2016 09:01:43(GMT) - Validation::linuxLibChecks - Line: Done.

Therefore, the CCS installer is correctly detecting a more recent GLIBC version is needed to run CCS 6.2.0 on CentOS 6.8 64-bit, but the installer is not warning the user on the install GUI.