Differences

This shows you the differences between two versions of the page.

--- bash:environment_variables:ld_library_path [2021/02/02 13:38] – peter
+++ bash:environment_variables:ld_library_path [2021/02/02 13:40] (current) – [BASH - Environment Variables - LD_LIBRARY_PATH] peter
@@ Line 5: / Line 5: @@
 Multiple directories can be listed, separated by a colon (:), and this list is then searched before the compiled-in search path(s), and the standard locations (typically /lib, /usr/lib, …).
-This can be used for:
+LD_LIBRARY_PATH can be used for:
   * testing new versions of a shared library against an already compiled application
@@ Line 11: / Line 11: @@
   * creating a self-contained, relocatable(!) environment for larger applications, such that they do not depend on (changing) system libraries – many software vendors use that approach.
-Problems with using LD_LIBRARY_PATH include:
+<WRAP alert>
+**ALERT:**  Problems with using **LD_LIBRARY_PATH** include:
   * **Security**:   Directories specified in LD_LIBRARY_PATH get searched before(!) the standard locations.
@@ Line 26: / Line 27: @@
   * **Non-Fixing of actual issue**.  Very often it is used as a crutch to fix a problem that could have been avoided by other means; but the actual issue is not fixed, as this workaround becomes relied upon.
     * These settings get dependent on this crutch – and if it is eventually taken away, they start to stumble (i.e. fail to run).
+</WRAP>
 ----