I want to install Trillian onto my CentOS 7 box. I went to www.trillian.im/get/linux/6.1/linux.html and downloaded the rpm package trillian-6.1.0.5-1.fc25.x86_64.rpm.
It was my understanding that using:
$ yum install trillian-6.1.0.5-1.fc25.x86_64.rpm
would install the package and also check for and retrieve any other files needed to resolve dependencies. It apparently didn't find any:
Marking trillian-6.1.0.5-1.fc25.x86_64.rpm to be installed
Resolving Dependencies
--> Running transaction check
---> Package trillian.x86_64 0:6.1.0.5-1.fc25 will be installed
--> Finished Dependency Resolution
Dependencies Resolved
================================================================================
Package Arch Version Repository Size
================================================================================
Installing:
trillian x86_64 6.1.0.5-1.fc25 /trillian-6.1.0.5-1.fc25.x86_64 30 M
Transaction Summary
================================================================================
Install 1 Package
.
.
.
Installed:
trillian.x86_64 0:6.1.0.5-1.fc25
Complete!
However, when I try to run the program, I get this:
$ trillian
trillian: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by trillian)
trillian: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by trillian)
I've tried to find a way to download those specific libraries.
Best Answer
Commentary on YUM & deps
YUM does do this. But it's only as good as the RPM specifies. In this case your RPM states that it'll work with any GLIBC > 2.13 but it clearly was built with a specific version of GLIBC, and will only work if the appropriate GCC symbols are available on the system:
You can use
rpm -qpR <rpm>
to determine what dependencies it requires.More on your issue
The heart of your issue is you're attempting to use a package that was built using a different version of the GCC compiler vs. what run time libraries are actually available on your OS.
In your case you're on CentOS 7.x and you really cannot mix RPMs across Fedora & CentOS like this, or at least you shouldn't.
If you look at what package owns that shared library:
You can also investigate the shared library itself to see what GCC symbols it supports:
And finally look to see if it includes the ones that this RPM's binaries is looking for:
No surprises here, this
.so
library doesn't include the symbols for either of those versions of GCC, hence the error.What to do?
The typical ways you deal with this are either:
Get just the
libstdc++.so.6
library from some other tool (many apps opt to include libraries for easier deployment/setup/installation) and point to it via yourLD_LIBRARY_PATH
. You typically do it like this:Run the app in a VM
Given the similarities between Fedora & CentOS I've had good success with many of the above. You could try #5, and try one of the older Fedora RPMs on their website to see if it was built with CentOS's version of GCC symbols.
References