summaryrefslogtreecommitdiffstats
path: root/share/man/man5/elf.5
diff options
context:
space:
mode:
Diffstat (limited to 'share/man/man5/elf.5')
-rw-r--r--share/man/man5/elf.512
1 files changed, 6 insertions, 6 deletions
diff --git a/share/man/man5/elf.5 b/share/man/man5/elf.5
index 2be201f..e4c1137 100644
--- a/share/man/man5/elf.5
+++ b/share/man/man5/elf.5
@@ -51,7 +51,7 @@ the file.
.Pp
Applications which wish to process ELF binary files for their native
architecture only should include
-.Pa elf.h
+.In elf.h
in their source code.
These applications should need to refer to
all the types and structures by their generic names
@@ -63,11 +63,11 @@ regardless whether the host is 32-bit or 64-bit.
.Pp
Should an application need to process ELF files of an unknown
architecture then the application needs to include both
-.Pa sys/elf32.h
+.In sys/elf32.h
and
-.Pa sys/elf64.h
+.In sys/elf64.h
instead of
-.Pa elf.h .
+.In elf.h .
Furthermore, all types and structures need to be identified by either
.Dq Elf32_xxx
or
@@ -78,9 +78,9 @@ or
.Dq ELF64_xxx .
.Pp
Whatever the system's architecture is, it will always include
-.Pa sys/elf_common.h
+.In sys/elf_common.h
as well as
-.Pa sys/elf_generic.h .
+.In sys/elf_generic.h .
.Pp
These header files describe the above mentioned headers as C structures
and also include structures for dynamic sections, relocation sections and
OpenPOWER on IntegriCloud