version krb5support_0_MIT not defined

[Jeff Blaine]

> Yeah, I think you have two libraries with different contents but the same
> SONAME, at which point the run-time linker is only going to load the
> library once (whichever one it finds first) into a given process space.

This is a correct assessment.

-bash-3.2# readelf -d /usr/lib64/libcom_err.so 
/usr/rcf-krb5/lib/libcom_err.so /usr/lib64/libkrb5support.so 
/usr/rcf-krb5/lib/libkrb5support.so | grep SONAME
  0x000000000000000e (SONAME)  Library soname: [libcom_err.so.2]
  0x000000000000000e (SONAME)  Library soname: [libcom_err.so.3]
  0x000000000000000e (SONAME)  Library soname: [libkrb5support.so.0]
  0x000000000000000e (SONAME)  Library soname: [libkrb5support.so.0]
-bash-3.2#

It would appear that I cannot control library location
preference in this situation, but I am certainly open
to any last chance suggestions.

This raises the question to me (largely ignorant past this
point): Isn't this incorrect?  I'd think that an incompatible
library issue like this means something was not incremented
when it should have been, no?