[PATCH] Add --print-dirs option for ldconfig

[Dan Nicholson]

On Sat, May 12, 2012 at 3:57 AM, Andreas Schwab <schwab@linux-m68k.org> wrote:
> Dan Nicholson <dbn.lists@gmail.com> writes:
>
>> 2. A canonical representation of the system library paths. Right now
>> it's usually /lib:/usr/lib on x86 and /lib64:/lib:/usr/lib64:/usr/lib
>> on x86_64, I think. I only know that from convention, though. What if
>> I'm on a Debian system?
>
> Everything departing from the default is in /etc/ld.so.conf.

What's "the default"? I don't see it recorded in any glibc
documentation. Unless you're "in the know", how would you know that
/libx32 was now a valid directory? Why should I have to detect if I'm
on a 32 or 64 bit system and then guess what the system directories
are? What if the system path is changed like on Debian? Why should I
go dig through /etc/ld.so.conf and /etc/ld.so.conf.d when ldconfig is
already parsing those files just fine? Why can't glibc just tell me
what the paths are?

ldconfig seems like the perfect place to get this information.
ldconfig = dynamic linker configuration. Seems reasonable for it to
tell you what the configuration is.

--
Dan