Bug 20218 - LD_RUN_PATH vs. LD_LIBRARY_PATH
Summary: LD_RUN_PATH vs. LD_LIBRARY_PATH
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: binutils
Version: 6.2
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jakub Jelinek
QA Contact: David Lawrence
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-11-02 16:05 UTC by Bertold Kolics
Modified: 2007-04-18 16:29 UTC (History)
0 users

(edit)
Clone Of:
(edit)
Last Closed: 2000-11-02 16:05:53 UTC


Attachments (Terms of Use)

Description Bertold Kolics 2000-11-02 16:05:50 UTC
The man page of ld states that it uses the LD_RUN_PATH variable to look for
libraries that are linked with a given binary. However, in fact, the
LD_LIBRARY_PATH variable is used. This is confusing.

I could not find any man page which mentioned LD_LIBRARY_PATH.

Comment 1 Jakub Jelinek 2000-11-03 15:34:24 UTC
LD_RUN_PATH variable is used by the linker (ld) the same way as -rpath
argument to ld is used (LD_RUN_PATH is used if -rpath is not specified).
However, if some binary is linked without LD_RUN_PATH being set in environment
(resp. -rpath specified on ld command line) and you want to change the paths
used to look for libraries at runtime, you use the LD_LIBRARY_PATH variable
which is used by the dynamic linker (/lib/ld-linux.so.*).


Note You need to log in before you can comment on or make changes to this bug.