{ "mode": "man", "parameter": "ld-linux", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/ld-linux/8/json", "generated": "2026-10-04T13:52:50Z", "synopsis": "The dynamic linker can be run either indirectly by running some dynamically linked program or\nshared object (in which case no command-line options to the dynamic linker can be passed and,\nin the ELF case, the dynamic linker which is stored in the .interp section of the program is\nexecuted) or directly by running:\n/lib/ld-linux.so.* [OPTIONS] [PROGRAM [ARGUMENTS]]", "sections": { "NAME": { "content": "ld.so, ld-linux.so - dynamic linker/loader\n", "subsections": [] }, "SYNOPSIS": { "content": "The dynamic linker can be run either indirectly by running some dynamically linked program or\nshared object (in which case no command-line options to the dynamic linker can be passed and,\nin the ELF case, the dynamic linker which is stored in the .interp section of the program is\nexecuted) or directly by running:\n\n/lib/ld-linux.so.* [OPTIONS] [PROGRAM [ARGUMENTS]]\n", "subsections": [] }, "DESCRIPTION": { "content": "The programs ld.so and ld-linux.so* find and load the shared objects (shared libraries)\nneeded by a program, prepare the program to run, and then run it.\n\nLinux binaries require dynamic linking (linking at run time) unless the -static option was\ngiven to ld(1) during compilation.\n\nThe program ld.so handles a.out binaries, a binary format used long ago. The program\nld-linux.so* (/lib/ld-linux.so.1 for libc5, /lib/ld-linux.so.2 for glibc2) handles binaries\nthat are in the more modern ELF format. Both programs have the same behavior, and use the\nsame support files and programs (ldd(1), ldconfig(8), and /etc/ld.so.conf).\n\nWhen resolving shared object dependencies, the dynamic linker first inspects each dependency\nstring to see if it contains a slash (this can occur if a shared object pathname containing\nslashes was specified at link time). If a slash is found, then the dependency string is in‐\nterpreted as a (relative or absolute) pathname, and the shared object is loaded using that\npathname.\n\nIf a shared object dependency does not contain a slash, then it is searched for in the fol‐\nlowing order:\n\n(1) Using the directories specified in the DTRPATH dynamic section attribute of the binary\nif present and DTRUNPATH attribute does not exist. Use of DTRPATH is deprecated.\n\n(2) Using the environment variable LDLIBRARYPATH, unless the executable is being run in\nsecure-execution mode (see below), in which case this variable is ignored.\n\n(3) Using the directories specified in the DTRUNPATH dynamic section attribute of the bi‐\nnary if present. Such directories are searched only to find those objects required by\nDTNEEDED (direct dependencies) entries and do not apply to those objects' children,\nwhich must themselves have their own DTRUNPATH entries. This is unlike DTRPATH, which\nis applied to searches for all children in the dependency tree.\n\n(4) From the cache file /etc/ld.so.cache, which contains a compiled list of candidate shared\nobjects previously found in the augmented library path. If, however, the binary was\nlinked with the -z nodefaultlib linker option, shared objects in the default paths are\nskipped. Shared objects installed in hardware capability directories (see below) are\npreferred to other shared objects.\n\n(5) In the default path /lib, and then /usr/lib. (On some 64-bit architectures, the default\npaths for 64-bit shared objects are /lib64, and then /usr/lib64.) If the binary was\nlinked with the -z nodefaultlib linker option, this step is skipped.\n", "subsections": [ { "name": "Dynamic string tokens", "content": "In several places, the dynamic linker expands dynamic string tokens:\n\n• In the environment variables LDLIBRARYPATH, LDPRELOAD, and LDAUDIT,\n\n• inside the values of the dynamic section tags DTNEEDED, DTRPATH, DTRUNPATH, DTAUDIT,\nand DTDEPAUDIT of ELF binaries,\n\n• in the arguments to the ld.so command line options --audit, --library-path, and --preload\n(see below), and\n\n• in the filename arguments to the dlopen(3) and dlmopen(3) functions.\n\nThe substituted tokens are as follows:\n\n$ORIGIN (or equivalently ${ORIGIN})\nThis expands to the directory containing the program or shared object. Thus, an ap‐\nplication located in somedir/app could be compiled with\n\ngcc -Wl,-rpath,'$ORIGIN/../lib'\n\nso that it finds an associated shared object in somedir/lib no matter where somedir is\nlocated in the directory hierarchy. This facilitates the creation of \"turn-key\" ap‐\nplications that do not need to be installed into special directories, but can instead\nbe unpacked into any directory and still find their own shared objects.\n\n$LIB (or equivalently ${LIB})\nThis expands to lib or lib64 depending on the architecture (e.g., on x86-64, it ex‐\npands to lib64 and on x86-32, it expands to lib).\n\n$PLATFORM (or equivalently ${PLATFORM})\nThis expands to a string corresponding to the processor type of the host system (e.g.,\n\"x8664\"). On some architectures, the Linux kernel doesn't provide a platform string\nto the dynamic linker. The value of this string is taken from the ATPLATFORM value\nin the auxiliary vector (see getauxval(3)).\n\nNote that the dynamic string tokens have to be quoted properly when set from a shell, to pre‐\nvent their expansion as shell or environment variables.\n" } ] }, "OPTIONS": { "content": "--argv0 string (since glibc 2.33)\nSet argv[0] to the value string before running the program.\n\n--audit list\nUse objects named in list as auditors. The objects in list are delimited by colons.\n\n--glibc-hwcaps-mask list\nonly search built-in subdirectories if in list.\n\n--glibc-hwcaps-prepend list\nSearch glibc-hwcaps subdirectories in list.\n", "subsections": [ { "name": "--inhibit-cache", "content": "Do not use /etc/ld.so.cache.\n\n--library-path path\nUse path instead of LDLIBRARYPATH environment variable setting (see below). The\nnames ORIGIN, LIB, and PLATFORM are interpreted as for the LDLIBRARYPATH environment\nvariable.\n\n--inhibit-rpath list\nIgnore RPATH and RUNPATH information in object names in list. This option is ignored\nwhen running in secure-execution mode (see below). The objects in list are delimited\nby colons or spaces.\n\n--list List all dependencies and how they are resolved.\n\n--list-diagnostics (since glibc 2.33)\nPrint system diagnostic information in a machine-readable format, such as some inter‐\nnal loader variables, the auxiliary vector (see getauxval(3)), and the environment\nvariables. On some architectures, the command might print additional information\n(like the cpu features used in GNU indirect function selection on x86). --list-tun‐\nables (since glibc 2.33) Print the names and values of all tunables, along with the\nminimum and maximum allowed values.\n\n--preload list (since glibc 2.30)\nPreload the objects specified in list. The objects in list are delimited by colons or\nspaces. The objects are preloaded as explained in the description of the LDPRELOAD\nenvironment variable below.\n\nBy contrast with LDPRELOAD, the --preload option provides a way to perform preloading\nfor a single executable without affecting preloading performed in any child process\nthat executes a new program.\n", "long": "--inhibit-cache" }, { "name": "--verify", "content": "Verify that program is dynamically linked and this dynamic linker can handle it.\n", "long": "--verify" } ] }, "ENVIRONMENT": { "content": "Various environment variables influence the operation of the dynamic linker.\n", "subsections": [ { "name": "Secure-execution mode", "content": "For security reasons, if the dynamic linker determines that a binary should be run in secure-\nexecution mode, the effects of some environment variables are voided or modified, and fur‐\nthermore those environment variables are stripped from the environment, so that the program\ndoes not even see the definitions. Some of these environment variables affect the operation\nof the dynamic linker itself, and are described below. Other environment variables treated\nin this way include: GCONVPATH, GETCONFDIR, HOSTALIASES, LOCALDOMAIN, LDAUDIT, LDDEBUG,\nLDDEBUGOUTPUT, LDDYNAMICWEAK, LDHWCAPMASK, LDLIBRARYPATH, LDORIGINPATH, LDPRELOAD,\nLDPROFILE, LDSHOWAUXV, LOCALDOMAIN, LOCPATH, MALLOCTRACE, NISPATH, NLSPATH, RE‐\nSOLVHOSTCONF, RESOPTIONS, TMPDIR, and TZDIR.\n\nA binary is executed in secure-execution mode if the ATSECURE entry in the auxiliary vector\n(see getauxval(3)) has a nonzero value. This entry may have a nonzero value for various rea‐\nsons, including:\n\n• The process's real and effective user IDs differ, or the real and effective group IDs dif‐\nfer. This typically occurs as a result of executing a set-user-ID or set-group-ID pro‐\ngram.\n\n• A process with a non-root user ID executed a binary that conferred capabilities to the\nprocess.\n\n• A nonzero value may have been set by a Linux Security Module.\n" }, { "name": "Environment variables", "content": "Among the more important environment variables are the following:\n\nLDASSUMEKERNEL (from glibc 2.2.3 to glibc 2.36)\nEach shared object can inform the dynamic linker of the minimum kernel ABI version\nthat it requires. (This requirement is encoded in an ELF note section that is view‐\nable via readelf -n as a section labeled NTGNUABITAG.) At run time, the dynamic\nlinker determines the ABI version of the running kernel and will reject loading shared\nobjects that specify minimum ABI versions that exceed that ABI version.\n\nLDASSUMEKERNEL can be used to cause the dynamic linker to assume that it is running\non a system with a different kernel ABI version. For example, the following command\nline causes the dynamic linker to assume it is running on Linux 2.2.5 when loading the\nshared objects required by myprog:\n\n$ LDASSUMEKERNEL=2.2.5 ./myprog\n\nOn systems that provide multiple versions of a shared object (in different directories\nin the search path) that have different minimum kernel ABI version requirements,\nLDASSUMEKERNEL can be used to select the version of the object that is used (depen‐\ndent on the directory search order).\n\nHistorically, the most common use of the LDASSUMEKERNEL feature was to manually se‐\nlect the older LinuxThreads POSIX threads implementation on systems that provided both\nLinuxThreads and NPTL (which latter was typically the default on such systems); see\npthreads(7).\n\nLDBINDNOW (since glibc 2.1.1)\nIf set to a nonempty string, causes the dynamic linker to resolve all symbols at pro‐\ngram startup instead of deferring function call resolution to the point when they are\nfirst referenced. This is useful when using a debugger.\n\nLDLIBRARYPATH\nA list of directories in which to search for ELF libraries at execution time. The\nitems in the list are separated by either colons or semicolons, and there is no sup‐\nport for escaping either separator. A zero-length directory name indicates the cur‐\nrent working directory.\n\nThis variable is ignored in secure-execution mode.\n\nWithin the pathnames specified in LDLIBRARYPATH, the dynamic linker expands the to‐\nkens $ORIGIN, $LIB, and $PLATFORM (or the versions using curly braces around the\nnames) as described above in Dynamic string tokens. Thus, for example, the following\nwould cause a library to be searched for in either the lib or lib64 subdirectory below\nthe directory containing the program to be executed:\n\n$ LDLIBRARYPATH='$ORIGIN/$LIB' prog\n\n(Note the use of single quotes, which prevent expansion of $ORIGIN and $LIB as shell\nvariables!)\n\nLDPRELOAD\nA list of additional, user-specified, ELF shared objects to be loaded before all oth‐\ners. This feature can be used to selectively override functions in other shared ob‐\njects.\n\nThe items of the list can be separated by spaces or colons, and there is no support\nfor escaping either separator. The objects are searched for using the rules given un‐\nder DESCRIPTION. Objects are searched for and added to the link map in the left-to-\nright order specified in the list.\n\nIn secure-execution mode, preload pathnames containing slashes are ignored. Further‐\nmore, shared objects are preloaded only from the standard search directories and only\nif they have set-user-ID mode bit enabled (which is not typical).\n\nWithin the names specified in the LDPRELOAD list, the dynamic linker understands the\ntokens $ORIGIN, $LIB, and $PLATFORM (or the versions using curly braces around the\nnames) as described above in Dynamic string tokens. (See also the discussion of quot‐\ning under the description of LDLIBRARYPATH.)\n\nThere are various methods of specifying libraries to be preloaded, and these are han‐\ndled in the following order:\n\n(1) The LDPRELOAD environment variable.\n\n(2) The --preload command-line option when invoking the dynamic linker directly.\n\n(3) The /etc/ld.so.preload file (described below).\n\nLDTRACELOADEDOBJECTS\nIf set (to any value), causes the program to list its dynamic dependencies, as if run\nby ldd(1), instead of running normally.\n\nThen there are lots of more or less obscure variables, many obsolete or only for internal\nuse.\n\nLDAUDIT (since glibc 2.4)\nA list of user-specified, ELF shared objects to be loaded before all others in a sepa‐\nrate linker namespace (i.e., one that does not intrude upon the normal symbol bindings\nthat would occur in the process) These objects can be used to audit the operation of\nthe dynamic linker. The items in the list are colon-separated, and there is no sup‐\nport for escaping the separator.\n\nLDAUDIT is ignored in secure-execution mode.\n\nThe dynamic linker will notify the audit shared objects at so-called auditing check‐\npoints—for example, loading a new shared object, resolving a symbol, or calling a sym‐\nbol from another shared object—by calling an appropriate function within the audit\nshared object. For details, see rtld-audit(7). The auditing interface is largely\ncompatible with that provided on Solaris, as described in its Linker and Libraries\nGuide, in the chapter Runtime Linker Auditing Interface.\n\nWithin the names specified in the LDAUDIT list, the dynamic linker understands the\ntokens $ORIGIN, $LIB, and $PLATFORM (or the versions using curly braces around the\nnames) as described above in Dynamic string tokens. (See also the discussion of quot‐\ning under the description of LDLIBRARYPATH.)\n\nSince glibc 2.13, in secure-execution mode, names in the audit list that contain\nslashes are ignored, and only shared objects in the standard search directories that\nhave the set-user-ID mode bit enabled are loaded.\n\nLDBINDNOT (since glibc 2.1.95)\nIf this environment variable is set to a nonempty string, do not update the GOT\n(global offset table) and PLT (procedure linkage table) after resolving a function\nsymbol. By combining the use of this variable with LDDEBUG (with the categories\nbindings and symbols), one can observe all run-time function bindings.\n\nLDDEBUG (since glibc 2.1)\nOutput verbose debugging information about operation of the dynamic linker. The con‐\ntent of this variable is one of more of the following categories, separated by colons,\ncommas, or (if the value is quoted) spaces:\n\nhelp Specifying help in the value of this variable does not run the specified\nprogram, and displays a help message about which categories can be speci‐\nfied in this environment variable.\n\nall Print all debugging information (except statistics and unused; see below).\n\nbindings Display information about which definition each symbol is bound to.\n\nfiles Display progress for input file.\n\nlibs Display library search paths.\n\nreloc Display relocation processing.\n\nscopes Display scope information.\n\nstatistics Display relocation statistics.\n\nsymbols Display search paths for each symbol look-up.\n\nunused Determine unused DSOs.\n\nversions Display version dependencies.\n\nSince glibc 2.3.4, LDDEBUG is ignored in secure-execution mode, unless the file\n/etc/suid-debug exists (the content of the file is irrelevant).\n\nLDDEBUGOUTPUT (since glibc 2.1)\nBy default, LDDEBUG output is written to standard error. If LDDEBUGOUTPUT is de‐\nfined, then output is written to the pathname specified by its value, with the suffix\n\".\" (dot) followed by the process ID appended to the pathname.\n\nLDDEBUGOUTPUT is ignored in secure-execution mode.\n\nLDDYNAMICWEAK (since glibc 2.1.91)\nBy default, when searching shared libraries to resolve a symbol reference, the dynamic\nlinker will resolve to the first definition it finds.\n\nOld glibc versions (before glibc 2.2), provided a different behavior: if the linker\nfound a symbol that was weak, it would remember that symbol and keep searching in the\nremaining shared libraries. If it subsequently found a strong definition of the same\nsymbol, then it would instead use that definition. (If no further symbol was found,\nthen the dynamic linker would use the weak symbol that it initially found.)\n\nThe old glibc behavior was nonstandard. (Standard practice is that the distinction\nbetween weak and strong symbols should have effect only at static link time.) In\nglibc 2.2, the dynamic linker was modified to provide the current behavior (which was\nthe behavior that was provided by most other implementations at that time).\n\nDefining the LDDYNAMICWEAK environment variable (with any value) provides the old\n(nonstandard) glibc behavior, whereby a weak symbol in one shared library may be over‐\nridden by a strong symbol subsequently discovered in another shared library. (Note\nthat even when this variable is set, a strong symbol in a shared library will not\noverride a weak definition of the same symbol in the main program.)\n\nSince glibc 2.3.4, LDDYNAMICWEAK is ignored in secure-execution mode.\n\nLDHWCAPMASK (from glibc 2.1 to glibc 2.38)\nMask for hardware capabilities. Since glibc 2.26, the option might be ignored if\nglibc does not support tunables.\n\nLDORIGINPATH (since glibc 2.1)\nPath where the binary is found.\n\nSince glibc 2.4, LDORIGINPATH is ignored in secure-execution mode.\n\nLDPOINTERGUARD (from glibc 2.4 to glibc 2.22)\nSet to 0 to disable pointer guarding. Any other value enables pointer guarding, which\nis also the default. Pointer guarding is a security mechanism whereby some pointers\nto code stored in writable program memory (return addresses saved by setjmp(3) or\nfunction pointers used by various glibc internals) are mangled semi-randomly to make\nit more difficult for an attacker to hijack the pointers for use in the event of a\nbuffer overrun or stack-smashing attack. Since glibc 2.23, LDPOINTERGUARD can no\nlonger be used to disable pointer guarding, which is now always enabled.\n\nLDPROFILE (since glibc 2.1)\nThe name of a (single) shared object to be profiled, specified either as a pathname or\na soname. Profiling output is appended to the file whose name is: $LDPROFILEOUTPUT/\n$LDPROFILE.profile.\n\nSince glibc 2.2.5, LDPROFILE uses a different default path in secure-execution mode.\n\nLDPROFILEOUTPUT (since glibc 2.1)\nDirectory where LDPROFILE output should be written. If this variable is not defined,\nor is defined as an empty string, then the default is /var/tmp.\n\nLDPROFILEOUTPUT is ignored in secure-execution mode; instead /var/profile is always\nused.\n\nLDSHOWAUXV (since glibc 2.1)\nIf this environment variable is defined (with any value), show the auxiliary array\npassed up from the kernel (see also getauxval(3)).\n\nSince glibc 2.3.4, LDSHOWAUXV is ignored in secure-execution mode.\n\nLDTRACEPRELINKING (from glibc 2.4 to glibc 2.35)\nIf this environment variable is defined, trace prelinking of the object whose name is\nassigned to this environment variable. (Use ldd(1) to get a list of the objects that\nmight be traced.) If the object name is not recognized, then all prelinking activity\nis traced.\n\nLDUSELOADBIAS (from glibc 2.3.3 to glibc 2.35)\nBy default (i.e., if this variable is not defined), executables and prelinked shared\nobjects will honor base addresses of their dependent shared objects and (nonprelinked)\nposition-independent executables (PIEs) and other shared objects will not honor them.\nIf LDUSELOADBIAS is defined with the value 1, both executables and PIEs will honor\nthe base addresses. If LDUSELOADBIAS is defined with the value 0, neither executa‐\nbles nor PIEs will honor the base addresses.\n\nSince glibc 2.3.3, this variable is ignored in secure-execution mode.\n\nLDVERBOSE (since glibc 2.1)\nIf set to a nonempty string, output symbol versioning information about the program if\nthe LDTRACELOADEDOBJECTS environment variable has been set.\n\nLDWARN (since glibc 2.1.3)\nIf set to a nonempty string, warn about unresolved symbols.\n\nLDPREFERMAP32BITEXEC (x86-64 only; since glibc 2.23)\nAccording to the Intel Silvermont software optimization guide, for 64-bit applica‐\ntions, branch prediction performance can be negatively impacted when the target of a\nbranch is more than 4 GB away from the branch. If this environment variable is set\n(to any value), the dynamic linker will first try to map executable pages using the\nmmap(2) MAP32BIT flag, and fall back to mapping without that flag if that attempt\nfails. NB: MAP32BIT will map to the low 2 GB (not 4 GB) of the address space.\n\nBecause MAP32BIT reduces the address range available for address space layout random‐\nization (ASLR), LDPREFERMAP32BITEXEC is always disabled in secure-execution mode.\n" } ] }, "FILES": { "content": "/lib/ld.so\na.out dynamic linker/loader\n\n/lib/ld-linux.so.{1,2}\nELF dynamic linker/loader\n\n/etc/ld.so.cache\nFile containing a compiled list of directories in which to search for shared objects\nand an ordered list of candidate shared objects. See ldconfig(8).\n\n/etc/ld.so.preload\nFile containing a whitespace-separated list of ELF shared objects to be loaded before\nthe program. See the discussion of LDPRELOAD above. If both LDPRELOAD and\n/etc/ld.so.preload are employed, the libraries specified by LDPRELOAD are preloaded\nfirst. /etc/ld.so.preload has a system-wide effect, causing the specified libraries\nto be preloaded for all programs that are executed on the system. (This is usually\nundesirable, and is typically employed only as an emergency remedy, for example, as a\ntemporary workaround to a library misconfiguration issue.)\n\nlib*.so*\nshared objects\n", "subsections": [] }, "NOTES": { "content": "", "subsections": [ { "name": "Legacy Hardware capabilities (from glibc 2.5 to glibc 2.37)", "content": "Some shared objects are compiled using hardware-specific instructions which do not exist on\nevery CPU. Such objects should be installed in directories whose names define the required\nhardware capabilities, such as /usr/lib/sse2/. The dynamic linker checks these directories\nagainst the hardware of the machine and selects the most suitable version of a given shared\nobject. Hardware capability directories can be cascaded to combine CPU features. The list\nof supported hardware capability names depends on the CPU. The following names are currently\nrecognized:\n\nAlpha ev4, ev5, ev56, ev6, ev67\n\nMIPS loongson2e, loongson2f, octeon, octeon2\n" }, { "name": "PowerPC", "content": "4xxmac, altivec, arch205, arch206, booke, cellbe, dfp, efpdouble, efpsingle, fpu,\nicsnoop, mmu, notb, pa6t, power4, power5, power5+, power6x, ppc32, ppc601, ppc64,\nsmt, spe, ucache, vsx\n\nSPARC flush, muldiv, stbar, swap, ultra3, v9, v9v, v9v2\n\ns390 dfp, eimm, esan3, etf3enh, g5, highgprs, hpage, ldisp, msa, stfle, z900, z990, z9-109,\nz10, zarch\n" }, { "name": "x86 (32-bit only)", "content": "acpi, apic, clflush, cmov, cx8, dts, fxsr, ht, i386, i486, i586, i686, mca, mmx, mtrr,\npat, pbe, pge, pn, pse36, sep, ss, sse, sse2, tm\n\nThe legacy hardware capabilities support has the drawback that each new feature added grows\nthe search path exponentially, because it has to be added to every combination of the other\nexisting features.\n\nFor instance, on x86 32-bit, if the hardware supports i686 and sse2, the resulting search\npath will be i686/sse2:i686:sse2:.. A new capability newcap will set the search path to new‐\ncap/i686/sse2:newcap/i686:newcap/sse2:newcap:i686/sse2:i686:sse2:.\n" }, { "name": "glibc Hardware capabilities (from glibc 2.33)", "content": "glibc 2.33 added a new hardware capability scheme,\nwhere under each CPU architecture, certain levels can be defined, grouping support for\ncertain features or special instructions. Each architecture level has a fixed set of\npaths that it adds to the dynamic linker search list, depending on the hardware of the\nmachine. Since each new architecture level is not combined with previously existing\nones, the new scheme does not have the drawback of growing the dynamic linker search\nlist uncontrollably.\n\nFor instance, on x86 64-bit, if the hardware supports x8664-v3 (for instance Intel Haswell\nor AMD Excavator), the resulting search path will be glibc-hwcaps/x86-64-v3:glibc-hw‐\ncaps/x86-64-v2:. The following paths are currently supported, in priority order.\n" }, { "name": "PowerPC (64-bit little-endian only)", "content": "power10, power9\n" }, { "name": "s390 (64-bit only)", "content": "z16, z15, z14, z13\n" }, { "name": "x86 (64-bit only)", "content": "x86-64-v4, x86-64-v3, x86-64-v2\n\nglibc 2.37 removed support for the legacy hardware capabilities.\n" } ] }, "SEE ALSO": { "content": "ld(1), ldd(1), pldd(1), sprof(1), dlopen(3), getauxval(3), elf(5), capabilities(7), rtld-au‐\ndit(7), ldconfig(8), sln(8)\n\nLinux man-pages 6.7 2024-02-12 ld.so(8)", "subsections": [] } }, "summary": "ld.so, ld-linux.so - dynamic linker/loader", "flags": [ { "flag": "", "long": "--inhibit-cache", "arg": null, "description": "Do not use /etc/ld.so.cache. --library-path path Use path instead of LDLIBRARYPATH environment variable setting (see below). The names ORIGIN, LIB, and PLATFORM are interpreted as for the LDLIBRARYPATH environment variable. --inhibit-rpath list Ignore RPATH and RUNPATH information in object names in list. This option is ignored when running in secure-execution mode (see below). The objects in list are delimited by colons or spaces. --list List all dependencies and how they are resolved. --list-diagnostics (since glibc 2.33) Print system diagnostic information in a machine-readable format, such as some inter‐ nal loader variables, the auxiliary vector (see getauxval(3)), and the environment variables. On some architectures, the command might print additional information (like the cpu features used in GNU indirect function selection on x86). --list-tun‐ ables (since glibc 2.33) Print the names and values of all tunables, along with the minimum and maximum allowed values. --preload list (since glibc 2.30) Preload the objects specified in list. The objects in list are delimited by colons or spaces. The objects are preloaded as explained in the description of the LDPRELOAD environment variable below. By contrast with LDPRELOAD, the --preload option provides a way to perform preloading for a single executable without affecting preloading performed in any child process that executes a new program." }, { "flag": "", "long": "--verify", "arg": null, "description": "Verify that program is dynamically linked and this dynamic linker can handle it." } ], "examples": [], "see_also": [ { "name": "ld", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/ld/1/json" }, { "name": "ldd", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/ldd/1/json" }, { "name": "pldd", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/pldd/1/json" }, { "name": "sprof", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/sprof/1/json" }, { "name": "dlopen", "section": "3", "url": "https://www.chedong.com/phpMan.php/man/dlopen/3/json" }, { "name": "getauxval", "section": "3", "url": "https://www.chedong.com/phpMan.php/man/getauxval/3/json" }, { "name": "elf", "section": "5", "url": "https://www.chedong.com/phpMan.php/man/elf/5/json" }, { "name": "capabilities", "section": "7", "url": "https://www.chedong.com/phpMan.php/man/capabilities/7/json" }, { "name": "dit", "section": "7", "url": "https://www.chedong.com/phpMan.php/man/dit/7/json" }, { "name": "ldconfig", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/ldconfig/8/json" }, { "name": "sln", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/sln/8/json" }, { "name": "ld.so", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/ld.so/8/json" } ] }