Do I have libbigloo* drivers linked incorrectly?

[stan]

On Sun, 27 Feb 2011 20:04:59 -0600
"Robert G. (Doc) Savage" <dsavage at peaknet.net> wrote:

> Lately every time I update my system I see umpteen cycles of messages
> complaining about a group of files that are "not a symbolic link":
> 
> /sbin/ldconfig: /usr/lib/libbigloosrfi27_es-3.4a.so is not a symbolic
> link /sbin/ldconfig: /usr/lib/libbigloocrypto_es-3.4a.so is not a
> symbolic link /sbin/ldconfig: /usr/lib/libbigloothread_es-3.4a.so is
> not a symbolic
> link 

[snip]
 
> Each of these loops takes a noticeable amount of time -- especially on
> this old 32-bit system. Thirty-two iterations of this loop add
> substantially to the total update time. I see counterpart messages
> when updating a 64-bit system.

Are you sure it is the warnings that are taking the time?  When
ldconfig is run, it has to go through the libraries and that takes
time.  Perhaps you are associating that time with the warning messages.

> 
> When I look at all the libbigloo* files in /usr/lib, the *_u-3.4a.so
> files are soft linked to *_s-3.4a.so files. There are also
> *_eu-3.4a.so and *_es-3.4a.so versions of those files available for
> linking.
> 
> Do I have the correct links?

This is a bigloo issue, known but apparently harmless except for the
issues you raise above.

https://bugzilla.redhat.com/show_bug.cgi?id=628799