mirror of https://github.com/mkerrisk/man-pages
ld.so.8: Describe interpretation of slashes in dependency strings
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
parent
8e9ea025e1
commit
15d116d5c9
12
man8/ld.so.8
12
man8/ld.so.8
|
@ -40,8 +40,16 @@ support files and programs
|
|||
and
|
||||
.IR /etc/ld.so.conf .
|
||||
.LP
|
||||
The shared libraries needed by the program are searched for
|
||||
in the following order:
|
||||
When resolving library dependencies,
|
||||
the dynamic linker first inspects each dependency
|
||||
string to see if it contains a slash (this can occur if
|
||||
a library pathname containing slashes was specified at link time).
|
||||
If a slash is found, then the dependency string is interpreted as
|
||||
a (relative or absolute) pathname,
|
||||
and the library is loaded using that pathname.
|
||||
.LP
|
||||
If a library dependency does not contain a slash,
|
||||
then it is searched for in the following order:
|
||||
.IP o 3
|
||||
(ELF only) Using the directories specified in the
|
||||
DT_RPATH dynamic section attribute
|
||||
|
|
Loading…
Reference in New Issue