I have a... well, it's not really a problem, more of an anomaly. I just
upgraded my libc from 5.0.9 (yes, it's old, but it's what came with my
Slackware) to 5.4.38, and I tried updating the links with ldconfig.
Here is the problem. Everything works fine, as far as I can tell. But the
list given by ldconfig -v doesn't include a line of the form "libc.so.5 =>
libc.so.5.4.38", or a line like "libm.so.5 => libm.so.5.0.9". What it does
have is:
/sbin/ldconfig: version 1.7.3
[irrelevant removed]
/lib:
libm.so.5.0.9 => libm.so.5.0.9
[irrelevant removed]
libm.so.5 => libm.so.5
[irrelevant removed]
nion => libc.so.5.4.38
[irrelevant removed]
The libm links point to themselves rather than to each other, and I've got
some ridiculous 'nion' link to libc. As I say, nothing's broken (AFAIK) but
it is disconcerting.
I'd like to know three things:
1) Are these anomalies likely to affect the operation of the system?
2) How can I fix them so that they won't be a problem?
3) Where does ldconfig get this nion from, considering it is not present in
the source code?
The first two questions are the important ones, the third - let's just say,
it will set my mind at ease.
Thanks in advance for any help anyone can offer me on these anomalies.
-----------------------------------------------------------------------
#include <disclaimer.h>
Matthew Palmer | Technophile, programmer, and old style hacker.
[EMAIL PROTECTED] | E-mail me for my PGP key.
