From db4163b1119c9caad681932587bd2aaa83903bfa Mon Sep 17 00:00:00 2001 From: Michael Kerrisk Date: Sat, 29 Dec 2007 17:21:41 +0000 Subject: [PATCH] ffixes --- man5/elf.5 | 20 +++++++++++++++----- 1 file changed, 15 insertions(+), 5 deletions(-) diff --git a/man5/elf.5 b/man5/elf.5 index 492aae6ff..e6007f994 100644 --- a/man5/elf.5 +++ b/man5/elf.5 @@ -333,7 +333,9 @@ This byte identifies the version of the ABI to which the object is targeted. This field is used to distinguish among incompatible versions of an ABI. The interpretation of this version number -is dependent on the ABI identified by the EI_OSABI field. +is dependent on the ABI identified by the +.B EI_OSABI +field. Applications conforming to this specification use the value 0. .TP .BR EI_PAD @@ -341,14 +343,18 @@ Start of padding. These bytes are reserved and set to zero. Programs which read them should ignore them. -The value for EI_PAD will change in +The value for +.B EI_PAD +will change in the future if currently unused bytes are given meanings. .TP .BR EI_BRAND Start of architecture identification. .TP .BR EI_NIDENT -The size of the e_ident array. +The size of the +.I e_ident +array. .\" .El .RE .TP @@ -1561,7 +1567,9 @@ There are macros for packing and unpacking the binding and type fields: .BR ELF32_ST_BIND (info) or .BR ELF64_ST_BIND (info) -extract a binding from an st_info value. +extract a binding from an +.I st_info +value. .IP .BR ELF32_ST_TYPE (info) or @@ -1575,7 +1583,9 @@ value. or .BR ELF64_ST_INFO "(bind, type)" .br -convert a binding and a type into an st_info value. +convert a binding and a type into an +.I st_info +value. .RE .\" .El .TP