How to print the ld linker search path

Question

What is the way to print the search paths that in looked by ld in the order it searches

User · Answer

You can do this by executing the following command:

ld --verbose | grep SEARCH_DIR | tr -s ' ;' \\012

gcc passes a few extra -L paths to the linker, which you can list with the following command:

gcc -print-search-dirs | sed '/^lib/b 1;d;:1;s,/[^/.][^/]*/\.\./,/,;t 1;s,:[^=]*=,:;,;s,;,;  ,g' | tr \; \\012

The answers suggesting to use ld.so.conf and ldconfig are not correct because they refer to the paths searched by the runtime dynamic linker (i.e. whenever a program is executed), which is not the same as the path searched by ld (i.e. whenever a program is linked).

User · Answer

The most compatible command I ve found for gcc and clang on Linux  thanks to armando sano      gcc -m64 -Xlinker --verbose  2 gt  dev null   grep SEARCH   sed  s SEARCH DIR                      1 n g     grep -vE        if you give -m32  it will output the correct library directories   Examples on my machine   for g   -m64    usr x86 64-linux-gnu lib64  usr i686-linux-gnu lib64  usr local lib x86 64-linux-gnu  usr local lib64  lib x86 64-linux-gnu  lib64  usr lib x86 64-linux-gnu  usr lib64  usr local lib  lib  usr lib   for g   -m32    usr i686-linux-gnu lib32  usr local lib32  lib32  usr lib32  usr local lib i386-linux-gnu  usr local lib  lib i386-linux-gnu  lib  usr lib i386-linux-gnu  usr lib

User · Answer

Mac version    ld -v 2  don t know how to get detailed paths  output   Library search paths       usr lib      usr local lib Framework search paths       Library Frameworks       System Library Frameworks

User · Answer

I m not sure that there is any option for simply printing the full effective search path   But  the search path consists of directories specified by -L options on the command line  followed by directories added to the search path by SEARCH DIR        directives in the linker script s    So you can work it out if you can see both of those  which you can do as follows   If you re invoking ld directly    The -L options are whatever you ve said they are  To see the linker script  add the --verbose option   Look for the SEARCH DIR        directives  usually near the top of the output    Note that these are not necessarily the same for every invocation of ld -- the linker has a number of different built-in default linker scripts  and chooses between them based on various other linker options     If you re linking via gcc    You can pass the -v option to gcc so that it shows you how it invokes the linker   In fact  it normally does not invoke ld directly  but indirectly via a tool called collect2  which lives in one of its internal directories   which in turn invokes ld   That will show you what -L options are being used  You can add -Wl --verbose to the gcc options to make it pass --verbose through to the linker  to see the linker script as described above

User · Answer

The question is tagged Linux  but maybe this works as well under Linux   gcc -Xlinker -v   Under Mac OS X  this prints       PROGRAM ld  PROJECT ld64-224 1 configured to support archs  armv6 armv7 armv7s arm64 i386 x86 64 armv6m armv7m armv7em Library search paths       Applications Xcode app Contents Developer Platforms MacOSX platform Developer SDKs MacOSX10 9 sdk usr lib Framework search paths       Applications Xcode app Contents Developer Platforms MacOSX platform Developer SDKs MacOSX10 9 sdk System Library Frameworks          The -Xlinker option of gcc above just passes -v to ld  However   ld -v   doesn t print the search path

User · Answer

On Linux  you can use ldconfig  which maintains the ld so configuration and cache  to print out the directories search by ld so with  ldconfig -v 2 gt  dev null   grep -v     t    ldconfig -v prints out the directories search by the linker  without a leading tab  and the shared libraries found in those directories  with a leading tab   the grep gets the directories  On my machine  this line prints out   usr lib64 atlas   usr lib llvm   usr lib64 llvm   usr lib64 mysql   usr lib64 nvidia   usr lib64 tracker-0 12   usr lib wine   usr lib64 wine   usr lib64 xulrunner-2   lib   lib64   usr lib   usr lib64   usr lib64 nvidia tls   hwcap  0x8000000000000000   lib i686   hwcap  0x0008000000000000   lib64 tls   hwcap  0x8000000000000000   usr lib sse2   hwcap  0x0000000004000000   usr lib64 tls   hwcap  0x8000000000000000   usr lib64 sse2   hwcap  0x0000000004000000    The first paths  without hwcap in the line  are either built-in or read from  etc ld so conf  The linker can then search additional directories under the basic library search path  with names like sse2 corresponding to additional CPU capabilities  These paths  with hwcap in the line  can contain additional libraries tailored for these  CPU capabilities   One final note  using -p instead of -v above searches the ld so cache instead

[linux] How to print the ld(linker) search path

Examples related to linux

Examples related to gcc

Examples related to linker

Examples related to ld