Missing 64 bit libraries on RHEL 4.5

[Ian Dennison_1]

I have having a product vendor tell me that the 64 bit libraries are missing from /usr/lib64 for the product. The message is

./sapinst: error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory

The library file is present in /usr/lib. I tried to download the package recommended but the checksig fails,...
[root@ULA003 ~]# rpm -checksig compat-libstdc++-33-3.2.3-61.x86_64.rpm
compat-libstdc++-33-3.2.3-61.x86_64.rpm: (SHA1) DSA sha1 md5 (GPG) NOT OK (MISSING KEYS: GPG#a7048f8d)
[root@ULA003 ~]#

Is this vendor giving me the right info? Share and Enjoy! Ian

[Ivan Ferreira]

First, ensure you have the key imported:

rpm --import /usr/share/rhn/RPM-GPG-KEY

Verify the signature. From the output above, you can say that the package was installed but is damaged. You should reinstall the package.

You can then check the signature of the downloaded package with:

rpm -K .rpm

[Steven E. Protter]

Shalom,

Those packages are available on the isntall disks. After you get the GPG key installed you should be able to do anything you want with them.

SEP

[Ian Dennison_1]

Gents,

Thanks for the input so far.

The package is only downloaded as an RPM, I have yet to install it (I dont want to install until I know it is valid). I have looked for the rpm on the install CDs and it is not there.

I perform an "rpm -K" after the GPG import and it still fails.

[root@ULA003 ~]# rpm --import /usr/share/rhn/RPM-GPG-KEY
[root@ULA003 ~]# rpm -K compat-libstdc++-33-3.2.3-61.x86_64.rpm
compat-libstdc++-33-3.2.3-61.x86_64.rpm: (SHA1) DSA sha1 md5 (GPG) NOT OK (MISSING KEYS: GPG#a7048f8d)
[root@ULA003 ~]#

Am I downloading the wrong version? Mine is an AMD64 Chipset, is this imcompatible with x86_64?

Share and Enjoy! Ian

[Ivan Ferreira · Accepted solution]

The package for the architecture is correct. From where are you downloading the package? The MISSING KEYS output means that you don't have the gpg key for that package, and the sha1 md5 NOT OK output means that the package is corrupt.

[Ian Dennison_1]

Ivan,

I think the version I downloaded was for Fedora 6, not RHEL 4. I found this on "rpm.pbone.net", using a google search. I clicked on the "other versions" and I don't see "RHEL 4" on the list. Does that mean this OS does not have the packlage released for it?

I am guessing that the GPGKEY is used to check compatability of RPMs against current OS levels?

I am downloading gcc bundle for RHEL 5 to see if this is compatibile.

Share and Enjoy! Ian

[Ivan Ferreira]

If you don't have access to Red Hat Network you can use the CentOS package available here:

ftp.centos.org/4.5/os/x86_64/CentOS/RPMS/

[TY 007]

Hello Ian,

>> rpm -K compat-libstdc++-33-3.2.3-61.x86_64.rpm

Get hold of the RHEL4 Update 5 OS Installation DVD Media.

compat-libstdc++-33-3.2.3-47.3.x86_64.rpm --> /RedHat/RPMS directory ?

Thanks

[Ian Dennison_1]

Found the problem. Illiterate SAP Support Staff did not read the pre-requisites for their package and a set of Legacy Development Libraries was not installed.

Sorted and working, thanks for everyones input. and did you beat your BASIS Admin today?

Share and Enjoy! Ian