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 /sbin/ldconfig: /usr/lib/libbigloopthread_es-3.4a.so is not a symbolic link /sbin/ldconfig: /usr/lib/libbigloosrfi1_es-3.4a.so is not a symbolic link /sbin/ldconfig: /usr/lib/libbigloomail_es-3.4a.so is not a symbolic link /sbin/ldconfig: /usr/lib/libbiglootext_es-3.4a.so is not a symbolic link /sbin/ldconfig: /usr/lib/libbigloopkgcomp_es-3.4a.so is not a symbolic link /sbin/ldconfig: /usr/lib/libbigloocalendar_es-3.4a.so is not a symbolic link /sbin/ldconfig: /usr/lib/libbiglooweb_es-3.4a.so is not a symbolic link /sbin/ldconfig: /usr/lib/libbigloostreamer_es-3.4a.so is not a symbolic link /sbin/ldconfig: /usr/lib/libbigloosqlite_es-3.4a.so is not a symbolic link /sbin/ldconfig: /usr/lib/libbigloopackrat_es-3.4a.so is not a symbolic link /sbin/ldconfig: /usr/lib/libbigloopkglib_es-3.4a.so is not a symbolic link /sbin/ldconfig: /usr/lib/libbigloomultimedia_es-3.4a.so is not a symbolic link
Tonight every one of the following had to grind thru one of these 15-part cycles:
Installing : 1:qt-4.7.1-17.fc14.i686 38/258 Updating : 1:qt-x11-4.7.1-17.fc14.i686 40/258 Updating : gnuradio-3.2.2-9.fc14.i686 42/258 Updating : usrp-3.2.2-9.fc14.i686 43/258 Updating : 1:qt-webkit-4.7.1-17.fc14.i686 45/258 Updating : 32:bind-libs-9.7.3-1.fc14.i686 46/258 Updating : 2:gimp-libs-2.6.11-6.fc14.i686 48/258 Updating : kdepimlibs-4.5.5-2.fc14.i686 50/258 Updating : kdepimlibs-akonadi-4.5.5-2.fc14.i686 53/258 Updating : 32:bind-9.7.3-1.fc14.i686 56/258 Updating : exiv2-libs-0.20-3.fc14.i686 61/258 Updating : libCg-3.0.0015-1.fc14.i686 62/258 Updating : gnuradio-devel-3.2.2-9.fc14.i686 72/258 Updating : google-perftools-1.7-1.fc14.i686 81/258 Updating : fuse-libs-2.8.5-4.fc14.i686 87/258 Updating : quvi-0.2.13-1.fc14.i686 88/258 Cleanup : erlang-typer-R14B-0.5.fc14.i686 180/258 Cleanup : yakuake-2.9.7-2.fc14.i686 183/258 Cleanup : gnuradio-3.2.2-7.fc14.i686 187/258 Cleanup : usrp-3.2.2-7.fc14.i686 188/258 Cleanup : 1:qbittorrent-2.6.5-1.fc14.i686 189/258 Cleanup : 1:qt-x11-4.7.1-7.fc14.i686 191/258 Cleanup : gimp-help-browser-2.6.11-1.fc14.i686 192/258 Cleanup : erlang-el_interface-R14B-0.5.fc14.i686 211/258 Cleanup : deltaiso-3.6-0.2.20100708git.fc14.i686 216/258 Cleanup : deltarpm-3.6-0.2.20100708git.fc14.i686 223/258 Cleanup : 32:bind-libs-9.7.2-5.P3.fc14.i686.i686 227/258 Cleanup : 2:gimp-libs-2.6.11-1.fc14.i686 228/258 Cleanup : xplanet-1.2.1-2.fc12.i686 229/258 Cleanup : minicom-2.5-1.fc14.i686 232/258 Cleanup : quvi-0.2.12-1.fc14.i686 238/258 Cleanup : soundtracker-0.6.8-8.fc12.i686 239/258
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.
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?
--Doc Savage Fairview Heights, IL
On Sun, 27 Feb 2011 20:04:59 -0600 "Robert G. (Doc) Savage" dsavage@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.
On Sun, 2011-02-27 at 19:56 -0700, stan wrote:
On Sun, 27 Feb 2011 20:04:59 -0600 "Robert G. (Doc) Savage" dsavage@peaknet.net wrote:
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.
You're almost certainly correct. My description was clearly a bit superficial.
This is a bigloo issue, known but apparently harmless except for the issues you raise above.
Thanks, Stan. Interesting notes in BZ. As long as I know what I'm seeing is benign, I won't worry about it.
--Doc Savage Fairview Heights, IL
-
Robert G. (Doc) Savage -
stan