[lkml]   [2001]   [Jun]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Is this part of newer filesystem hierarchy?
On Sat, 23 Jun 2001 19:09:12 -0600, 
"D. Stimits" <> wrote:
>There is a directory on RH 7.1 x86, /lib/i686/. When checking with ldd
>to various applications, as to which libc they link to, it turns out
>that the /lib/ is not used. They all seem to point at
>/lib/i686/ (this is the version with debugging symbols) by
>default. The odd thing is that there are NO LD_ style path variables set
>on this system, there is NO /etc/, and /etc/ does
>not contain any reference to /lib/i686/. So there is a question of just
>how it is possible for ld to use that directory and ignore /lib/ for

15 minutes with a few commands, man pages and the source of glibc will
show you this ...

# /sbin/ldconfig -p | fgrep -w libc (libc6, hwcap: 0x8000000000000, OS ABI: Linux 2.4.1) => /lib/i686/ (libc6, OS ABI: Linux 2.2.5) => /lib/

The data is coming from /etc/ which is build by ldconfig.
A quick scan of the source for ldconfig.c in glibc 2.2.2 shows that it
starts with standard paths /lib and /usr/lib then searches those
directories and all their subdirectories looking for libraries. That
explains why it finds /lib/i686 without being explicitly specified.

Note the hwcap entry in /lib/i686/ The dynamic linker no
longer takes the first entry it finds for a library, instead it looks
for the first entry that matches the current hardware. This is
required for machines like ia64 which can also run i386 binaries and
for sparc which can run 32 or 64 bit apps.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:55    [W:0.064 / U:0.076 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site