ld.so.8: wfix

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>

man8/ld.so.8

@@ -209,7 +209,7 @@ A nonzero value may have been set by a Linux Security Module.
 .SS Environment variables
 Among the more important environment variables are the following:
 .TP
-.BR LD_ASSUME_KERNEL " (glibc since 2.2.3)"
+.BR LD_ASSUME_KERNEL " (since glibc 2.2.3)"
 Each shared object can inform the dynamic linker of the minimum kernel ABI
 version that it requires.
 (This requirement is encoded in an ELF note section that is viewable via
@@ -251,7 +251,7 @@ LinuxThreads and NPTL
 see
 .BR pthreads (7).
 .TP
-.BR LD_BIND_NOW " (glibc since 2.1.1)"
+.BR LD_BIND_NOW " (since glibc 2.1.1)"
 If set to a nonempty string,
 causes the dynamic linker to resolve all symbols
 at program startup instead of deferring function call resolution to the point
@@ -329,7 +329,7 @@ instead of running normally.
 Then there are lots of more or less obscure variables,
 many obsolete or only for internal use.
 .TP
-.BR LD_AUDIT " (glibc since 2.4)"
+.BR LD_AUDIT " (since glibc 2.4)"
 A colon-separated list of user-specified, ELF shared objects
 to be loaded before all others in a separate linker namespace
 (i.e., one that does not intrude upon the normal symbol bindings that
@@ -351,12 +351,12 @@ as described in its
 in the chapter
 .IR "Runtime Linker Auditing Interface" .
 .TP
-.BR LD_BIND_NOT " (glibc since 2.1.95)"
+.BR LD_BIND_NOT " (since glibc 2.1.95)"
 If this environment variable is set to a nonempty string,
 do not update the GOT (global offset table) and PLT (procedure linkage table)
 after resolving a symbol.
 .TP
-.BR LD_DEBUG " (glibc since 2.1)"
+.BR LD_DEBUG " (since glibc 2.1)"
 Output verbose debugging information about the dynamic linker.
 If set to
 .BR all ,
@@ -408,7 +408,7 @@ is ignored in secure-execution mode, unless the file
 .IR /etc/suid\-debug
 exists (the content of the file is irrelevant).
 .TP
-.BR LD_DEBUG_OUTPUT " (glibc since 2.1)"
+.BR LD_DEBUG_OUTPUT " (since glibc 2.1)"
 File in which
 .B LD_DEBUG
 output should be written.
@@ -416,7 +416,7 @@ The default is standard error.
 .B LD_DEBUG_OUTPUT
 is ignored in secure-execution mode.
 .TP
-.BR LD_DYNAMIC_WEAK " (glibc since 2.1.91)"
+.BR LD_DYNAMIC_WEAK " (since glibc 2.1.91)"
 If this environment variable is defined (with any value),
 allow weak symbols to be overridden (reverting to old glibc behavior).
 .\" See weak handling
@@ -430,10 +430,10 @@ Since glibc 2.3.4,
 .B LD_DYNAMIC_WEAK
 is ignored in secure-execution mode.
 .TP
-.BR LD_HWCAP_MASK " (glibc since 2.1)"
+.BR LD_HWCAP_MASK " (since glibc 2.1)"
 Mask for hardware capabilities.
 .TP
-.BR LD_ORIGIN_PATH " (glibc since 2.1)"
+.BR LD_ORIGIN_PATH " (since glibc 2.1)"
 Path where the binary is found.
 Since glibc 2.4,
 .B LD_ORIGIN_PATH
@@ -457,13 +457,13 @@ Since glibc 2.23,
 can no longer be used to disable pointer guarding,
 which is now always enabled.
 .TP
-.BR LD_PROFILE " (glibc since 2.1)"
+.BR LD_PROFILE " (since glibc 2.1)"
 The name of a (single) shared object to be profiled,
 specified either as a pathname or a soname.
 Profiling output is appended to the file whose name is:
 "\fI$LD_PROFILE_OUTPUT\fP/\fI$LD_PROFILE\fP.profile".
 .TP
-.BR LD_PROFILE_OUTPUT " (glibc since 2.1)"
+.BR LD_PROFILE_OUTPUT " (since glibc 2.1)"
 Directory where
 .B LD_PROFILE
 output should be written.
@@ -475,7 +475,7 @@ is ignored in secure-execution mode; instead
 .IR /var/profile
 is always used.
 .TP
-.BR LD_SHOW_AUXV " (glibc since 2.1)"
+.BR LD_SHOW_AUXV " (since glibc 2.1)"
 If this environment variable is defined (with any value),
 show the auxiliary array passed up from the kernel (see also
 .BR getauxval (3)).
@@ -483,7 +483,7 @@ Since glibc 2.3.5,
 .B LD_SHOW_AUXV
 is ignored in secure-execution mode.
 .TP
-.BR LD_TRACE_PRELINKING " (glibc since 2.4)"
+.BR LD_TRACE_PRELINKING " (since glibc 2.4)"
 If this environment variable is defined (with any value),
 trace prelinking of the object whose name is assigned to
 this environment variable.
@@ -494,7 +494,7 @@ If the object name is not recognized,
 .\" (This is what seems to happen, from experimenting)
 then all prelinking activity is traced.
 .TP
-.BR LD_USE_LOAD_BIAS " (glibc since 2.3.3)"
+.BR LD_USE_LOAD_BIAS " (since glibc 2.3.3)"
 .\" http://sources.redhat.com/ml/libc-hacker/2003-11/msg00127.html
 .\" Subject: [PATCH] Support LD_USE_LOAD_BIAS
 .\" Jakub Jelinek
@@ -513,17 +513,17 @@ is defined with the value 0,
 neither executables nor PIEs will honor the base addresses.
 This variable is ignored in secure-execution mode.
 .TP
-.BR LD_VERBOSE " (glibc since 2.1)"
+.BR LD_VERBOSE " (since glibc 2.1)"
 If set to a nonempty string,
 output symbol versioning information about the
 program if the
 .B LD_TRACE_LOADED_OBJECTS
 environment variable has been set.
 .TP
-.BR LD_WARN " (ELF only; glibc since 2.1.3)
+.BR LD_WARN " (ELF only; since glibc 2.1.3)
 If set to a nonempty string, warn about unresolved symbols.
 .TP
-.BR LD_PREFER_MAP_32BIT_EXEC " (x86-64 only; glibc since 2.23)"
+.BR LD_PREFER_MAP_32BIT_EXEC " (x86-64 only; since glibc 2.23)"
 According to the Intel Silvermont software optimization guide, for 64-bit
 applications, branch prediction performance can be negatively impacted
 when the target of a branch is more than 4GB away from the branch.