Following Install Guide for CENTOS, scripts/install-prerequisites.sh error on Multilib version problems. Note that system was not a fresh CENTOS install and had OpenCPI previously installed. Error summary below. Complete console output attached.
--> Running transaction check
---> Package glibc-devel.i686 0:2.12-1.132.el6 will be updated
---> Package glibc-devel.x86_64 0:2.12-1.132.el6 will be updated
---> Package glibc-devel.i686 0:2.12-1.149.el6_6.5 will be an update
---> Package glibc-devel.x86_64 0:2.12-1.149.el6_6.5 will be an update
---> Package glibc-headers.x86_64 0:2.12-1.132.el6 will be updated
---> Package glibc-headers.x86_64 0:2.12-1.149.el6_6.5 will be an update
--> Finished Dependency Resolution
Error: Multilib version problems found. This often means that the root
cause is something else and multilib version checking is just
pointing out that there is a problem. Eg.:
1. You have an upgrade for libXext which is missing some
dependency that another package requires. Yum is trying to
solve this by installing an older version of libXext of the
different architecture. If you exclude the bad architecture
yum will tell you what the root cause is (which package
requires what). You can try redoing the upgrade with
--exclude libXext.otherarch ... this should give you an error
message showing the root cause of the problem.
2. You have multiple architectures of libXext installed, but
yum can only see an upgrade for one of those arcitectures.
If you don't want/need both architectures anymore then you
can remove the one with the missing update and everything
3. You have duplicate versions of libXext installed already.
You can use "yum check" to get yum show these errors.
...you can also use --setopt=protected_multilib=false to remove
this checking, however this is almost never the correct thing to
do as something else is very likely to go wrong (often causing
much more problems).
Protected multilib versions: libXext-1.3.2-2.1.el6.i686 != libXext-1.3.1-2.el6.x86_64
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest