在 分类下   暂无评论


  在 分类下   暂无评论



export LD_LIBRARY_PATH=/usr/lib64
export LD_PRELOAD=/usr/lib64


似乎这两个环境变量只对应用程序有效,对shell命令不起作用啊。想到lib64只是个软链接,真实文件是/usr/lib64/。而本身并不是库文件,可以把它理解为库文件的管理程序,而且它很特别。国外有个牛人是这么说的: is a pretty core part of your OS. It actually
runs every (64 bit) dynamic application. It's not a library as much as
an app itself, a handler that is called when you run an app.

Basically, when you run a dynamic app, the kernel first runs (or whatever name it is for your bitsize, distro, etc). then peers into your app, sees the libraries that you
need, sees any hard coded paths for the libraries (e.g. rpath's)
checks LD_LIBRARY_PATH, and then goes looking for all those libraries,
makes sure they match bitsizes, names, what have you. It then collects
all of those, loads them, and runs your app. If it can't find the
libs, it doesn't run your app. can not be affected by LD_LIBRARY_PATH because it is run
by the kernel, and the kernel does not load libraries like
does, it just has the one it's configured to run. Again, not a
library, so don't use library semantics (LD_LIBRARY_PATH) to change
how it's called. It does have environment variables that affect it
running - see man for details.





--library-path path Use path instead of LD_LIBRARY_PATH environment variable

setting (see below).




You have invoked `', the helper program for shared library executables.
This program usually lives in the file `/lib/', and special directives
in executable files using ELF shared libraries tell the system's program
loader to load the helper program from this file.  This helper program loads
the shared libraries needed by the program executable, prepares the program
to run, and runs it.  You may invoke this helper program directly from the
command line to load and run an ELF executable file; this is like executing
that file itself, but always uses this helper program from the file you
specified, instead of the helper program file specified in the executable
file you run.  This is mostly of use for maintainers to test new versions
of this helper program; chances are you did not intend to run this program.

--list                list all dependencies and how they are resolved
--verify              verify that given object really is a dynamically linked
            object we can handle
--inhibit-cache       Do not use /etc/
--library-path PATH   use given PATH instead of content of the environment
            variable LD_LIBRARY_PATH
--inhibit-rpath LIST  ignore RUNPATH and RPATH information in object names
            in LIST
--audit LIST          use objects named in LIST as auditors


/usr/lib64/ --library-path /usr/lib64/ /usr/bin/ln -s /usr/lib64 /lib64