PATCH: ldconfig.c considers ld.so.conf entries before /lib,/usr/lib

[Ben Collins]

On Wed, Aug 29, 2001 at 08:34:34PM -0700, Ulrich Drepper wrote:
> Dirk Eddelbuettel <edd@debian.org> writes:
> 
> > ldconfig -v [from Debian's libc6_2.2.4-1 package] reads /lib and /usr/lib
> > before it considers the directories in /etc/ld.so.conf.  This is in conflict
> > with ld.so(8) as well as ldconfig(8).
> 
> It's completely irrelevant what the man pages say.  If they are not in
> line with the implementation it's the implementation setting the
> standard.
> 
> The current way ldconfig works is how it worked ever since.  There is
> no reason to change it since this will have negative effects and might
> suddenly change the behavior of people's systems.

Not entirely true. From the original ldconfig.c in the ld.so sources:

        /* look ma, no defaults */
        if (!nodefault)
        {
            /* I guess the defaults aren't good enough */
            if ((extpath = get_extpath()))
            {
                for (cp = strtok(extpath, DIR_SEP); cp;
                     cp = strtok(NULL, DIR_SEP))
                    scan_dir(cp);
                free(extpath);
            }

            /* everybody needs these, don't they? */
            scan_dir("/usr/lib");
            scan_dir("/lib");
        }

get_extpath() retrieves the paths from the config file. So glibc 2.2.x
is not following the old "standard", which has worked for ages.

-- 
 .----------=======-=-======-=========-----------=====------------=-=-----.
/  Ben Collins  --  ...on that fantastic voyage...  --  Debian GNU/Linux   \
`  bcollins@debian.org  --  bcollins@openldap.org  --  bcollins@linux.com  '
 `---=========------=======-------------=-=-----=-===-======-------=--=---'