RPM packages depend on those pits Ld-linux-x86-64.so.2:bad ELF interpreter

Objective

When Rpm/dpkg installs a package, it often has a missing dependency class error, and often chooses to ignore the dependent installation, although it sometimes solves the problem at the moment, but digs a hole for the future.

It is often the case that the YUM/APT warehouse does not have the corresponding software or the appropriate version to use the RPM/DPKG installation package, which is mostly because of network restrictions or internal deployment of local libraries, or because YUM/APT warehouse configuration is not entirely caused by

This is to say, in the CentOS system at least to configure the base, updates, extras these three types of metadata address

Drop the pit.

After n long, when installing a package or yum update, the system reported a dependency error or version conflict ... such as glibc dependency error

1.GLIBC Ld-linux-x86-64.so.2:bad ELF Interpreter

At this point it is assumed that blindly uninstalling glibc and then installing the corresponding version may result in irreparable results ...
Once the glibc is uninstalled, how much of the system commands will not be used, because the need to rely on GLIBC library files, error is as follows
Ld-linux-x86-64.so.2:bad ELF Interpreter

If you happen to have BusyBox installed on your system, you can download and reinstall the GLIBC library file using the BusyBox tool

busybox wget http://mirror.centos.org/centos/6/os/x86_64/Packages/glibc-2.12-1.209.el6.x86_64.rpmbusybox rpm -ih glibc-2.12-1.209.el6.x86_64.rpm

2.error:package:glibc-2.12-1.209.el6.i686 (Base)

Description: The yum source has been configured and is terminated at the update times with the following details.

Error: Package: glibc-2.12-1.209.el6.i686 (Base)           Requires: glibc-common = 2.12-1.209.el6           Installed: glibc-common-2.12-1.209.el6_9.1.x86_64 (installed)               glibc-common = 2.12-1.209.el6_9.1           Available: glibc-common-2.12-1.209.el6.x86_64 (Base)               glibc-common = 2.12-1.209.el6 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest

Before dealing with a similar problem because there is no Yum source, manually install the update, but this time has been configured Yum, should not report such errors

yum clan allyum update

Anti-second interview several times, the problem is still. Check Yum configuration, find two copies of the same repo file, one is turned on, one is off, and the updates metadata is off
Keep a copy of the repo file, and set the metadata all to on, again update execution succeeded

3.has missing requires of

Such errors need to be performed after the update error

yum check

will appear, the error message is as follows

cloog-ppl-0.15.7-1.2.el6.x86_64 has missing requires of libppl.so.7()(64bit)cloog-ppl-0.15.7-1.2.el6.x86_64 has missing requires of libppl_c.so.2()(64bit)Error: check all

Probably meaning "has missing requires of" in front of the package is missing "has missing requires of" behind the library file
If you confirm that the package is optional, you can remove it first, if you cannot remove it, you need to install the corresponding missing library package, then you can update normally

Postscript

When installing a package separately RPM, you must install it with the missing dependencies if you encounter a dependency error
use--nodeps parameters , such as glibc and Glibc-common, to rely on each other to install

rpm -ih glibc.rpm glibc-common.rpm

What is missing depends on what is installed together, sometimes the system has installed the required packages, but the package version is slightly lower, need to upgrade, installation needs to be aware that at this time should be with the-u parameter upgrade package, not the-I parameter installation

rpm -Uh openssl-1.0.2.rpm

If the dependent error is encountered, upgrade the dependent packages together

Focus

The above problem uses YUM/APT installation method basically does not appear, so has one can access to the metadata warehouse is how important!
For the CentOS system, you must ensure that the OS, updates, extras the three metadata warehouse
For the configuration of the metadata warehouse, refer to the previous article

RPM package depends on those pits Ld-linux-x86-64.so.2:bad ELF interpreter