ldconfig bug?

[Kiri Wagstaff]

Hello,

I recently upgraded from glibc 2.1.3 to glibc 2.2.2.  The installation
process for 2.2.2 replaced my /sbin/ldconfig with a version that seems
to include a bug.  

When I run "ldconfig -v" with no other arguments, it does not look in
/lib or /usr/lib for libraries to add to the cache.  (You might
imagine the problems this causes, since the system cannot find
libc.so, among other things).  The man page would seem to indicate
that these locations are checked by default (and indeed, this is the
case for my "old" ldconfig, from ld.so-1.9.11-4mdk), but they aren't.
I tried editing /etc/ld.so.conf to explicitly include these
directories - and ldconfig *still* did not examine their contents.

If I run "ldconfig -v /lib /usr/lib", the correct behavior results.
Is this what was desired, or does this indicate a bug in this version
of ldconfig?

   Thanks for your time,

   Kiri

------------- Kiri Wagstaff, M.S. -------- address@hidden -------------
                              Elusive as dreams
                       Barely remembered in the morning
                          Love like a phantom flies
                            But held in the heart
                    It pales like the empty smile adorning
                        A statue with sightless eyes
                      -- Dan Fogelberg, Make Love Stay
-----------------------------------------------------------------------------