On 04/22/2013 12:22 PM, Richard W.M. Jones wrote:
On Mon, Apr 22, 2013 at 11:27:42AM +0200, Michael Schwendt wrote:
> 3) Funny things going on (f19 here), but haven't examined anything
> beyond this:
>
> # rpm -e openldap-devel
> # ldconfig -v|grep ldap
> libldap_r-2.4.so.2 -> libldap_r-2.4.so.2.9.1
> libldap-2.4.so.2 -> libldap-2.4.so.2.9.1
> # yum -y install openldap-devel
> # ldconfig -v|grep ldap
> libldap_r-2.4.so.2 -> libldap_r.so
> libldap-2.4.so.2 -> libldap.so
>
> That makes no sense.
Indeed. That looks like there's something wrong with ldconfig.
On my (now fixed) system I get the same output from ldconfig:
$ sudo ldconfig -v | grep ldap
ldconfig: Can't stat /libx32: No such file or directory
ldconfig: Path `/usr/lib' given more than once
ldconfig: Path `/usr/lib64' given more than once
ldconfig: Can't stat /usr/libx32: No such file or directory
libsmbldap.so.0 -> libsmbldap.so.0
libldap_r-2.4.so.2 -> libldap_r.so
libldap-2.4.so.2 -> libldap.so
which as you say makes no sense.
On the other hand, the links on the filesystem are still correct:
$ ll /usr/lib64/libldap-2.4.so.2
lrwxrwxrwx. 1 root root 20 Apr 22 09:26 /usr/lib64/libldap-2.4.so.2 ->
libldap-2.4.so.2.9.0
Rich.
Have you found out how this originally happened? I can't get any of my f18-f20
machines to this state.
--
Jan Synacek
Software Engineer, Red Hat