Would appreciate any help on how to deal with this kind of situation. I'm installing a software package that will allow me to back up my RH9 server and get this..
[root@profserv root]# rpm -ivh TIVsm-API.i386.rpm TIVsm-BA.i386.rpm
error: Failed dependencies:
libstdc++-libc6.2-2.so.3 is needed by TIVsm-API-5.2.3-0
libstdc++-libc6.1-1.so.2 is needed by TIVsm-BA-5.2.3-0
libstdc++-libc6.2-2.so.3 is needed by TIVsm-BA-5.2.3-0
[root@profserv root]# rpm -qa | grep libstd
libstdc++-3.2.2-5
libstdc++-devel-3.2.2-5
[root@profserv lib]# rpm -q libstdc++-3.2.2-5 --filesbypkg
libstdc++ /usr/lib/libstdc++.so.5
libstdc++ /usr/lib/libstdc++.so.5.0.3
Apparently the version that comes with RH9 is...
[root@profserv lib]# rpm -qp /root/libstdc++-2.96-110.i386.rpm --filesbypkg
libstdc++ /usr/lib/libstdc++-3-libc6.2-2-2.10.0.so
libstdc++ /usr/lib/libstdc++-libc6.2-2.so.3
So what should one do?
1. downgrade libstdc++? (probably breaking all sorts of other dependencies)
2. Somehow trick it to thinking the older one is installed hoping the newer one is backwards compatible (not sure how to do this.. create some kind of symbolic link?)?
3. smack yourself on the head and say doh!? i.e. give up realizing the software you're installing isn't compatible with your OS level?
Appreciate the help!
[root@profserv root]# rpm -ivh TIVsm-API.i386.rpm TIVsm-BA.i386.rpm
error: Failed dependencies:
libstdc++-libc6.2-2.so.3 is needed by TIVsm-API-5.2.3-0
libstdc++-libc6.1-1.so.2 is needed by TIVsm-BA-5.2.3-0
libstdc++-libc6.2-2.so.3 is needed by TIVsm-BA-5.2.3-0
[root@profserv root]# rpm -qa | grep libstd
libstdc++-3.2.2-5
libstdc++-devel-3.2.2-5
[root@profserv lib]# rpm -q libstdc++-3.2.2-5 --filesbypkg
libstdc++ /usr/lib/libstdc++.so.5
libstdc++ /usr/lib/libstdc++.so.5.0.3
Apparently the version that comes with RH9 is...
[root@profserv lib]# rpm -qp /root/libstdc++-2.96-110.i386.rpm --filesbypkg
libstdc++ /usr/lib/libstdc++-3-libc6.2-2-2.10.0.so
libstdc++ /usr/lib/libstdc++-libc6.2-2.so.3
So what should one do?
1. downgrade libstdc++? (probably breaking all sorts of other dependencies)
2. Somehow trick it to thinking the older one is installed hoping the newer one is backwards compatible (not sure how to do this.. create some kind of symbolic link?)?
3. smack yourself on the head and say doh!? i.e. give up realizing the software you're installing isn't compatible with your OS level?
Appreciate the help!