<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://aznot.com/index.php?action=history&amp;feed=atom&amp;title=Linux%2FLibrary_Path</id>
	<title>Linux/Library Path - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://aznot.com/index.php?action=history&amp;feed=atom&amp;title=Linux%2FLibrary_Path"/>
	<link rel="alternate" type="text/html" href="https://aznot.com/index.php?title=Linux/Library_Path&amp;action=history"/>
	<updated>2026-05-07T04:22:02Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.41.0</generator>
	<entry>
		<id>https://aznot.com/index.php?title=Linux/Library_Path&amp;diff=6106&amp;oldid=prev</id>
		<title>Kenneth: Created page with &quot;The usual dynamic linker on Linux uses a cache to find its libraries. The cache is stored in /etc/ld.so.cache, and is updated by ldconfig which looks on the paths it’s given...&quot;</title>
		<link rel="alternate" type="text/html" href="https://aznot.com/index.php?title=Linux/Library_Path&amp;diff=6106&amp;oldid=prev"/>
		<updated>2022-09-15T05:33:08Z</updated>

		<summary type="html">&lt;p&gt;Created page with &amp;quot;The usual dynamic linker on Linux uses a cache to find its libraries. The cache is stored in /etc/ld.so.cache, and is updated by ldconfig which looks on the paths it’s given...&amp;quot;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;The usual dynamic linker on Linux uses a cache to find its libraries. The cache is stored in /etc/ld.so.cache, and is updated by ldconfig which looks on the paths it’s given in /etc/ld.so.conf (and nowadays typically files in /etc/ld.so.conf.d). Its contents can be listed by running ldconfig -p.&lt;br /&gt;
&lt;br /&gt;
So there is no default value for LD_LIBRARY_PATH, default library lookup doesn’t need it at all. If LD_LIBRARY_PATH is defined, then it is used first, but doesn’t disable the other lookups (which also include a few default directories)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
ref [https://unix.stackexchange.com/questions/354295/what-is-the-default-value-of-ld-library-path&lt;br /&gt;
&lt;br /&gt;
The ld.so(8) manpage has the details:&lt;br /&gt;
&lt;br /&gt;
* If a shared object dependency does not contain a slash, then it is searched for in the following order:&lt;br /&gt;
&lt;br /&gt;
* Using the directories specified in the DT_RPATH dynamic section attribute of the binary if present and DT_RUNPATH attribute does not exist. Use of DT_RPATH is deprecated.&lt;br /&gt;
&lt;br /&gt;
* Using the environment variable LD_LIBRARY_PATH, unless the executable is being run in secure-execution mode (see below), in which case it is ignored.&lt;br /&gt;
&lt;br /&gt;
* Using the directories specified in the DT_RUNPATH dynamic section attribute of the binary if present.&lt;br /&gt;
&lt;br /&gt;
* From the cache file /etc/ld.so.cache, which contains a compiled list of candidate shared objects previously found in the augmented library path. If, however, the binary was linked with the -z nodeflib linker option, shared objects in the default paths are skipped. Shared objects installed in hardware capability directories (see below) are preferred to other shared objects.&lt;br /&gt;
&lt;br /&gt;
* In the default path /lib, and then /usr/lib. (On some 64-bit architectures, the default paths for 64-bit shared objects are /lib64, and then /usr/lib64.) If the binary was linked with the -z nodeflib linker option, this step is skipped.&lt;br /&gt;
&lt;br /&gt;
If LD_LIBRARY_PATH is not set or is empty, it is ignored. If it is set to empty values (with LD_LIBRARY_PATH=: for example), those empty values are interpreted as the current directory.&lt;/div&gt;</summary>
		<author><name>Kenneth</name></author>
	</entry>
</feed>