Hi Christian, Christian Weisgerber wrote on Sun, May 26, 2019 at 01:19:01AM -0000:
> Not sure what do about "ELF(3)" in elf(3). Index: elf.3 =================================================================== RCS file: /cvs/src/lib/libelf/elf.3,v retrieving revision 1.2 diff -u -p -r1.2 elf.3 --- elf.3 19 Mar 2019 02:31:35 -0000 1.2 +++ elf.3 26 May 2019 01:46:30 -0000 @@ -615,8 +615,11 @@ descriptor itself. .Xr ar 5 , .Xr elf 5 .Sh HISTORY -The original ELF(3) API was developed for Unix System V. -The current implementation of the ELF(3) API appeared in +The original +.Nm +API was developed for +.At V . +The current implementation of the API appeared in .Fx 7.0 . .Sh AUTHORS The ELF library was written by Index: elf_flagdata.3 =================================================================== RCS file: /cvs/src/lib/libelf/elf_flagdata.3,v retrieving revision 1.1 diff -u -p -r1.1 elf_flagdata.3 --- elf_flagdata.3 1 Feb 2019 05:27:37 -0000 1.1 +++ elf_flagdata.3 26 May 2019 01:46:30 -0000 @@ -34,7 +34,7 @@ .Nm elf_flagphdr , .Nm elf_flagscn , .Nm elf_flagshdr -.Nd manipulate flags associated with ELF(3) data structures +.Nd manipulate flags associated with ELF data structures .Sh LIBRARY .Lb libelf .Sh SYNOPSIS @@ -65,7 +65,9 @@ and .Ar scn denote the data structures whose flags need to be changed. These values should have been returned by prior calls to -functions in the ELF(3) API set: +functions in the +.Xr elf 3 +API set: .Bl -bullet -compact .It Argument @@ -175,7 +177,9 @@ function and the .Dv ELF_F_ARCHIVE and .Dv ELF_F_ARCHIVE_SYSV -flags are an extension to the ELF(3) API. +flags are an extension to the +.Xr elf 3 +API. .Sh ERRORS These functions may fail with the following errors: .Bl -tag -width "[ELF_E_RESOURCE]" Index: elf_open.3 =================================================================== RCS file: /cvs/src/lib/libelf/elf_open.3,v retrieving revision 1.1 diff -u -p -r1.1 elf_open.3 --- elf_open.3 1 Feb 2019 05:27:37 -0000 1.1 +++ elf_open.3 26 May 2019 01:46:30 -0000 @@ -43,7 +43,9 @@ The functions .Fn elf_open and .Fn elf_openmemory -are extensions to the ELF(3) API, for the internal use of the +are extensions to the +.Xr elf 3 +API, for the internal use of the Elftoolchain project. Portable applications should not use these functions. .Pp @@ -71,7 +73,9 @@ specifies the size of the memory area in The function returns a pointer to a ELF descriptor if successful, or NULL if an error occurred. .Sh COMPATIBILITY -These functions are non-standard extensions to the ELF(3) API set. +These functions are non-standard extensions to the +.Xr elf 3 +API set. .Pp The behavior of these functions differs from their counterparts .Xr elf_begin 3 Index: gelf.3 =================================================================== RCS file: /cvs/src/lib/libelf/gelf.3,v retrieving revision 1.1 diff -u -p -r1.1 gelf.3 --- gelf.3 1 Feb 2019 05:27:37 -0000 1.1 +++ gelf.3 26 May 2019 01:46:31 -0000 @@ -192,7 +192,10 @@ Copy back an ELF symbol table entry. .Xr elf 3 , .Xr elf 5 .Sh HISTORY -The GELF(3) API first appeared in System V Release 4. +The +.Nm +API first appeared in +.At V.4 . This implementation of the API first appeared in .Fx 7.0 . .Sh AUTHORS Index: gelf_newehdr.3 =================================================================== RCS file: /cvs/src/lib/libelf/gelf_newehdr.3,v retrieving revision 1.1 diff -u -p -r1.1 gelf_newehdr.3 --- gelf_newehdr.3 1 Feb 2019 05:27:38 -0000 1.1 +++ gelf_newehdr.3 26 May 2019 01:46:31 -0000 @@ -134,7 +134,9 @@ The function uses a type of .Ft "void *" for its returned value. -This differs from some other implementations of the ELF(3) API, which use an +This differs from some other implementations of the +.Xr elf 3 +API, which use an .Ft "unsigned long" return type. .Sh ERRORS Index: gelf_newphdr.3 =================================================================== RCS file: /cvs/src/lib/libelf/gelf_newphdr.3,v retrieving revision 1.1 diff -u -p -r1.1 gelf_newphdr.3 --- gelf_newphdr.3 1 Feb 2019 05:27:38 -0000 1.1 +++ gelf_newphdr.3 26 May 2019 01:46:31 -0000 @@ -103,7 +103,9 @@ The function uses a type of .Ft "void *" for its returned value. -This differs from some other implementations of the ELF(3) API, which use an +This differs from some other implementations of the +.Xr elf 3 +API, which use an .Ft "unsigned long" return type. .Sh ERRORS
