Executable and Linkable Format#FatELF: universal binaries for Linux

Each ELF file is made up of one ELF header, followed by file data. The data can include:

• Program header table, describing zero or more memory segments
• Section header table, describing zero or more sections
• Data referred to by entries in the program header table or section header table

File:ELF Executable and Linkable Format diagram by Ange Albertini.png

The segments contain information that is needed for run time execution of the file, while sections contain important data for linking and relocation. Any byte in the entire file can be owned by one section at most, and orphan bytes can occur which are unowned by any section.

The ELF header defines whether to use 32-bit or 64-bit addresses. The header contains three fields that are affected by this setting and offset other fields that follow them. The ELF header is 52 or 64 bytes long for 32-bit and 64-bit binaries, respectively.

|-

| colspan="2" | {{tt|0x08}} || colspan="2" | 1 || {{mono|e_ident[EI_ABIVERSION]}}

|Further specifies the ABI version. Its interpretation depends on the target ABI. Linux kernel (after at least 2.6) has no definition of it,{{cite web|url=http://lxr.linux.no/linux+v2.6.11/include/linux/elf.h#L380|title=LXR linux/include/linux/elf.h|website=linux.no|access-date=27 April 2015}} so it is ignored for statically linked executables. In that case, offset and size of EI_PAD are 8.

glibc 2.12+ in case {{mono|1=e_ident[EI_OSABI] == 3}} treats this field as ABI version of the dynamic linker:{{cite web|url=https://sourceware.org/ml/libc-alpha/2010-05/msg00000.html|title=glibc 2.12 announce}} it defines a list of dynamic linker's features,{{cite web|url=https://sourceware.org/git/?p=glibc.git;a=blob;f=libc-abis;h=e702f6ae245c1528f5a608df8cfae4f037809de2;hb=HEAD|title=sourceware.org Git - glibc.git/blob - libc-abis}} treats {{mono|e_ident[EI_ABIVERSION]}} as a feature level requested by the shared object (executable or dynamic library) and refuses to load it if an unknown feature is requested, i.e. {{mono|e_ident[EI_ABIVERSION]}} is greater than the largest known feature.{{cite web|url=https://sourceware.org/git/?p=glibc.git%3Ba%3Dblob%3Bf%3Dsysdeps%2Fgnu%2Fldsodefs.h%3Bh%3D253b4d934c5ca457ab5580a2a6398205e4f961ba%3Bhb%3DHEAD#l32|title=sourceware.org Git - glibc.git/blob - sysdeps/gnu/ldsodefs.h|access-date=2019-10-28|archive-date=2021-03-07|archive-url=https://web.archive.org/web/20210307223850/https://sourceware.org/git/?p=glibc.git%3Ba%3Dblob%3Bf%3Dsysdeps%2Fgnu%2Fldsodefs.h%3Bh%3D253b4d934c5ca457ab5580a2a6398205e4f961ba%3Bhb%3DHEAD#l32|url-status=dead}}

|-

| colspan="2" | {{tt|0x09}} || colspan="2" | 7 || {{mono|e_ident[EI_PAD]}}

|Reserved padding bytes. Currently unused. Should be filled with zeros and ignored when read.

|-

| colspan="2" | {{tt|0x10}} || colspan="2" | 2 || {{mono|e_type}}

| Identifies object file type.

|-

| colspan="2" | {{tt|0x12}} || colspan="2" | 2 || {{mono|e_machine}}

|Specifies target instruction set architecture. Some examples are:

|-

| colspan="2" | {{tt|0x14}} || colspan="2" | 4 || {{mono|e_version}}

|Set to 1 for the original version of ELF.

|-

| colspan="2" | {{tt|0x18}} || 4 || 8 || {{mono|e_entry}}

|This is the memory address of the entry point from where the process starts executing. This field is either 32 or 64 bits long, depending on the format defined earlier (byte 0x04). If the file doesn't have an associated entry point, then this holds zero.

|-

| {{tt|0x1C}} || {{tt|0x20}} || 4 || 8 || {{mono|e_phoff}}

|Points to the start of the program header table. It usually follows the file header immediately following this one, making the offset 0x34 or 0x40 for 32- and 64-bit ELF executables, respectively.

|-

| {{tt|0x20}} || {{tt|0x28}} || 4 || 8 || {{mono|e_shoff}}

|Points to the start of the section header table.

|-

| {{tt|0x24}} || {{tt|0x30}} || colspan="2" | 4 || {{mono|e_flags}}

|Interpretation of this field depends on the target architecture.

|-

| {{tt|0x28}} || {{tt|0x34}} || colspan="2" | 2 || {{mono|e_ehsize}}

|Contains the size of this header, normally 64 Bytes for 64-bit and 52 Bytes for 32-bit format.

|-

| {{tt|0x2A}} || {{tt|0x36}} || colspan="2" | 2 || {{mono|e_phentsize}}

|Contains the size of a program header table entry. As explained below, this will typically be 0x20 (32-bit) or 0x38 (64-bit).

|-

| {{tt|0x2C}} || {{tt|0x38}} || colspan="2" | 2 || {{mono|e_phnum}}

|Contains the number of entries in the program header table.

|-

| {{tt|0x2E}} || {{tt|0x3A}} || colspan="2" | 2 || {{mono|e_shentsize}}

|Contains the size of a section header table entry. As explained below, this will typically be 0x28 (32-bit) or 0x40 (64-bit).

|-

| {{tt|0x30}} || {{tt|0x3C}} || colspan="2" | 2 || {{mono|e_shnum}}

|Contains the number of entries in the section header table.

|-

| {{tt|0x32}} || {{tt|0x3E}} || colspan="2" | 2 || {{mono|e_shstrndx}}

|Contains index of the section header table entry that contains the section names.

|-

| {{tt|0x34}}

| {{tt|0x40}}

| colspan="3" |

|End of ELF Header (size).

|}

00000000 7f 45 4c 46 02 01 01 00 00 00 00 00 00 00 00 00 |.ELF............|

00000010 02 00 3e 00 01 00 00 00 c5 48 40 00 00 00 00 00 |..>......H@.....|

{{Cite web |title=Available lexers — Pygments |url=https://pygments.org/docs/lexers/#lexers-for-hexadecimal-dumps |access-date=2024-12-19 |website=pygments.org}}

The program header table tells the system how to create a process image. It is found at file offset {{mono|e_phoff}}, and consists of {{mono|e_phnum}} entries, each with size {{mono|e_phentsize}}. The layout is slightly different in 32-bit ELF vs 64-bit ELF, because the {{mono|p_flags}} are in a different structure location for alignment reasons. Each entry is structured as:

|-

| || {{tt|0x04}} || || 4 ||{{mono|p_flags}}||Segment-dependent flags (position for 64-bit structure).

|-

| {{tt|0x04}} || {{tt|0x08}} || 4 || 8||{{mono|p_offset}}||Offset of the segment in the file image.

|-

| {{tt|0x08}} || {{tt|0x10}} || 4 || 8 ||{{mono|p_vaddr}}||Virtual address of the segment in memory.

|-

| {{tt|0x0C}} || {{tt|0x18}} || 4 || 8 ||{{mono|p_paddr}}||On systems where physical address is relevant, reserved for segment's physical address.

|-

| {{tt|0x10}} || {{tt|0x20}} || 4 || 8 ||{{mono|p_filesz}}||Size in bytes of the segment in the file image. May be 0.

|-

| {{tt|0x14}} || {{tt|0x28}} || 4 || 8 ||{{mono|p_memsz}}||Size in bytes of the segment in memory. May be 0.

|-

| {{tt|0x18}} || || 4 || ||{{mono|p_flags}}||Segment-dependent flags (position for 32-bit structure). See above p_flags field for flag definitions.

|-

| {{tt|0x1C}} || {{tt|0x30}} || 4 || 8 ||{{mono|p_align}}||0 and 1 specify no alignment. Otherwise should be a positive, integral power of 2, with {{mono|p_vaddr}} equating {{mono|p_offset}} modulus {{mono|p_align}}.

|-

| {{tt|0x20}}

| {{tt|0x38}}

| colspan="3" |

|End of Program Header (size).

|}

|-

| colspan="2" |0x08

|4

|8

| {{tt|sh_flags}}

|Identifies the attributes of the section.

|-

| {{tt|0x0C}}

| {{tt|0x10}}

|4

|8

| {{tt|sh_addr}}

|Virtual address of the section in memory, for sections that are loaded.

|-

| {{tt|0x10}}

| {{tt|0x18}}

|4

|8

| {{tt|sh_offset}}

|Offset of the section in the file image.

|-

| {{tt|0x14}}

| {{tt|0x20}}

|4

|8

| {{tt|sh_size}}

|Size in bytes of the section. May be 0.

|-

| {{tt|0x18}}

| {{tt|0x28}}

| colspan="2" |4

| {{tt|sh_link}}

|Contains the section index of an associated section. This field is used for several purposes, depending on the type of section.

|-

| {{tt|0x1C}}

| {{tt|0x2C}}

| colspan="2" |4

| {{tt|sh_info}}

|Contains extra information about the section. This field is used for several purposes, depending on the type of section.

|-

| {{tt|0x20}}

| {{tt|0x30}}

|4

|8

| {{tt|sh_addralign}}

|Contains the required alignment of the section. This field must be a power of two.

|-

| {{tt|0x24}}

| {{tt|0x38}}

|4

|8

| {{tt|sh_entsize}}

|Contains the size, in bytes, of each entry, for sections that contain fixed-size entries. Otherwise, this field contains zero.

|-

| {{tt|0x28}}

| {{tt|0x40}}

| colspan="3" |

|End of Section Header (size).

|}

{{Main|GNU Binutils}}

• readelf is a Unix binary utility that displays information about one or more ELF files. A free software implementation is provided by GNU Binutils.
• elfutils provides alternative tools to GNU Binutils purely for Linux.{{cite web|url=https://sourceware.org/elfutils/|title=elfutils|website=sourceware.org|access-date=30 April 2017}}
• elfdump is a command for viewing ELF information in an ELF file, available under Solaris and FreeBSD.
• objdump provides a wide range of information about ELF files and other object formats. objdump uses the Binary File Descriptor library as a back-end to structure the ELF data.
• The Unix file utility can display some information about ELF files, including the instruction set architecture for which the code in a relocatable, executable, or shared object file is intended, or on which an ELF core dump was produced.

{{prose|date=November 2016}}

The ELF format has replaced older executable formats in various environments.

It has replaced a.out and COFF formats in Unix-like operating systems:

• Linux
• Solaris / Illumos
• IRIX
• FreeBSD{{Cite web | url=https://docs.freebsd.org/doc/4.9-RELEASE/usr/share/doc/handbook/binary-formats.html | title=Binary Formats | access-date=2019-03-31 | archive-date=2019-03-31 | archive-url=https://web.archive.org/web/20190331192807/https://docs.freebsd.org/doc/4.9-RELEASE/usr/share/doc/handbook/binary-formats.html | url-status=dead }}
• NetBSD
• OpenBSD
• Redox
• DragonFly BSD
• Syllable
• HP-UX (except for 32-bit PA-RISC programs which continue to use SOM)
• QNX Neutrino
• MINIX{{cite web |url=http://wiki.minix3.org/en/MinixReleases |title=MinixReleases – Minix Wiki |publisher=Wiki.minix3.org |access-date=2014-01-19 |url-status=dead |archive-url=https://web.archive.org/web/20130330150621/http://wiki.minix3.org/en/MinixReleases |archive-date=2013-03-30 }}

ELF has also seen some adoption in non-Unix operating systems, such as:

• OpenVMS, in its Itanium and amd64 versions{{Cite web |url=https://vmssoftware.com/pdfs/State_of_Port_20160906.pdf |title=Archived copy |access-date=2016-10-19 |archive-date=2020-09-15 |archive-url=https://web.archive.org/web/20200915215111/https://vmssoftware.com/pdfs/State_of_Port_20160906.pdf |url-status=dead }}
• BeOS Revision 4 and later for x86 based computers (where it replaced the Portable Executable format; the PowerPC version stayed with Preferred Executable Format)
• Haiku, an open source reimplementation of BeOS
• RISC OS{{cite web |url=http://www.riscos.info/index.php/GCCSDK |title=GCCSDK – RISC OS |publisher=Riscos.info |date=2012-04-22 |access-date=2014-01-19 |archive-date=2014-02-19 |archive-url=https://web.archive.org/web/20140219211405/http://www.riscos.info/index.php/GCCSDK |url-status=dead }}
• Stratus VOS, in PA-RISC and x86 versions
• SkyOS
• Fuchsia OS
• Z/TPF
• HPE NonStop OS{{cite web |url=http://h20628.www2.hp.com/km-ext/kmcsdirect/emr_na-c02543407-12.pdf |archive-url=https://web.archive.org/web/20180530042640/http://h20628.www2.hp.com/km-ext/kmcsdirect/emr_na-c02543407-12.pdf |url-status=dead |archive-date=2018-05-30 |title=Guardian Programmer's Guide |publisher=Hewlett Packard Enterprise |access-date=2018-05-30 }} p. 44 archived from [http://h20628.www2.hp.com/km-ext/kmcsdirect/emr_na-c02543407-12.pdf the original] {{Webarchive|url=https://web.archive.org/web/20180530042640/http://h20628.www2.hp.com/km-ext/kmcsdirect/emr_na-c02543407-12.pdf |date=2018-05-30 }} on 2018-5-30
• Deos

Microsoft Windows also uses the ELF format, but only for its Windows Subsystem for Linux compatibility system.{{Cite web|url=https://www.zdnet.com/article/under-the-hood-of-microsofts-windows-subsystem-for-linux/|title=Under the hood of Microsoft's Windows Subsystem for Linux|last=Foley|first=Mary Jo|website=ZDNet|access-date=2016-08-19}}

Some game consoles also use ELF:

• PlayStation Portable,PlayStation Portable use encrypted & relocated ELF : PSP PlayStation Vita, PlayStation, PlayStation 2, PlayStation 3, PlayStation 4, PlayStation 5
• GP2X
• Dreamcast
• GameCube
• Nintendo 64
• Wii
• Wii U

Other (operating) systems running on PowerPC that use ELF:

• AmigaOS 4, the ELF executable has replaced the prior Extended Hunk Format (EHF) which was used on Amigas equipped with PPC processor expansion cards.
• MorphOS
• AROS
• Café OS (The operating system run by the Wii U)

Some operating systems for mobile phones and mobile devices use ELF:

• Symbian OS v9 uses E32Image[https://web.archive.org/web/20091213034509/http://wiki.forum.nokia.com/index.php/E32Image Symbian OS executable file format] format that is based on the ELF file format;
• Sony Ericsson, for example, the W800i, W610, W300, etc.
• Siemens, the SGOLD and SGOLD2 platforms: from Siemens C65 to S75 and BenQ-Siemens E71/EL71;
• Motorola, for example, the E398, SLVR L7, v360, v3i (and all phone LTE2 which has the patch applied).
• Bada, for example, the Samsung Wave S8500.
• Nokia phones or tablets running the Maemo or the Meego OS, for example, the Nokia N900.
• Android uses ELF {{mono|.so}} (shared object

{{cite book

| last1 = Rosen

| first1 = Kenneth

| last2 = Host

| first2 = Douglas

| last3 = Klee

| first3 = Rachel

| last4 = Rosinski

| first4 = Richard

| title = UNIX: The Complete Reference

| url = https://books.google.com/books?id=2Et--84HIkwC

| edition = 2

| publisher = McGraw Hill Professional

| date = 2007

| page = 707

| isbn = 9780071706988

| access-date = 2017-06-08

| quote = Dynamically linked libraries are also called shared objects (.so).

}}

) libraries for the Java Native Interface.{{citation needed|date=February 2023}} With Android Runtime (ART), the default since Android 5.0 "Lollipop", all applications are compiled into native ELF binaries on installation.{{cite web |title=Android formats |url=https://lief-project.github.io/doc/latest/tutorials/10_android_formats.html |archive-url=https://archive.today/20230216233708/https://lief-project.github.io/doc/latest/tutorials/10_android_formats.html |access-date=17 Jan 2023 |archive-date=16 February 2023 |work=Quarks Lab |last=Thomas |first=Romain}} It's also possible to use native Linux software from package managers like Termux, or compile them from sources via Clang or GCC, that are available in repositories.

{{Anchor|np}}

Some phones can run ELF files through the use of a patch that adds assembly code to the main firmware, which is a feature known as ELFPack in the underground modding culture. The ELF file format is also used with the Atmel AVR (8-bit), AVR32

{{citation

| chapter-url=http://www.sco.com/developers/gabi/2009-10-26/ch4.eheader.html#e_machine

| title=System V Application Binary Interface

| chapter=Chapter 4: Object Files

| at=e_machine

| date=2009-10-26

}}

and with Texas Instruments MSP430 microcontroller architectures. Some implementations of Open Firmware can also load ELF files, most notably Apple's implementation used in almost all PowerPC machines the company produced.

• Solana uses ELF format for its on-chain programs (smart contracts). The platform processes ELF files compiled to BPF (Berkeley Packet Filter) byte-code, which are then deployed as shared objects and executed in Solana's runtime environment. The BPF loader validates and processes these ELF files during program deployment.{{Cite web

| url = https://solana.com/docs/core/programs

| title = Solana Programs

| date = 2024-11-11

| publisher = Solana Foundation

| access-date = 2024-11-11

| quote = Solana leverages the LLVM compiler infrastructure to compile programs into Executable and Linkable Format (ELF) files.}}

86open was a project to form consensus on a common binary file format for Unix and Unix-like operating systems on the common PC compatible x86 architecture, to encourage software developers to port to the architecture.{{cite web

|url= http://www.telly.org/86open-faq

|title= 86Open Frequently-Asked Questions

|access-date= 2007-06-06

|last= Leibovitch

|first= Evan

|date= 1997-12-23

|archive-url= https://web.archive.org/web/20070311032337/http://www.telly.org/86open-faq |archive-date= 2007-03-11}} The initial idea was to standardize on a small subset of Spec 1170, a predecessor of the Single UNIX Specification, and the GNU C Library (glibc) to enable unmodified binaries to run on the x86 Unix-like operating systems. The project was originally designated "Spec 150".

The format eventually chosen was ELF, specifically the Linux implementation of ELF, after it had turned out to be a de facto standard supported by all involved vendors and operating systems.

The group began email discussions in 1997 and first met together at the Santa Cruz Operation offices on August 22, 1997.

The steering committee was Marc Ewing, Dion Johnson, Evan Leibovitch, Bruce Perens, Andrew Roach, Bryan Wayne Sparks and Linus Torvalds. Other people on the project were Keith Bostic, Chuck Cranor, Michael Davidson, Chris G. Demetriou, Ulrich Drepper, Don Dugger, Steve Ginzburg, Jon "maddog" Hall, Ron Holt, Jordan Hubbard, Dave Jensen, Kean Johnston, Andrew Josey, Robert Lipe, Bela Lubkin, Tim Marsland, Greg Page, Ronald Joe Record, Tim Ruckle, Joel Silverstein, Chia-pi Tien, and Erik Troan. Operating systems and companies represented were BeOS, BSDI, FreeBSD, Intel, Linux, NetBSD, SCO and SunSoft.

The project progressed and in mid-1998, SCO began developing lxrun, an open-source compatibility layer able to run Linux binaries on OpenServer, UnixWare, and Solaris. SCO announced official support of lxrun at LinuxWorld in March 1999. Sun Microsystems began officially supporting lxrun for Solaris in early 1999,{{cite web

|url = http://www.mavetju.org/mail/view_message.php?list=freebsd-emulation&id=361608

|title = Bulletin on status of 86open at SCO

|access-date = 2008-05-06

|last = Record

|first = Ronald

|date = 1998-05-21

|url-status = dead

|archive-url = https://web.archive.org/web/20081208013909/http://www.mavetju.org/mail/view_message.php?list=freebsd-emulation&id=361608

|archive-date = 2008-12-08

}} and later moved to integrated support of the Linux binary format via Solaris Containers for Linux Applications.

With the BSDs having long supported Linux binaries (through a compatibility layer) and the main x86 Unix vendors having added support for the format, the project decided that Linux ELF was the format chosen by the industry and "declare[d] itself dissolved" on July 25, 1999.{{cite web

|url= https://www.telly.org/86open/

|title= The86open Project – Final Update

|access-date= 2007-05-06

|last= Leibovitch

|first= Evan

|date= 1999-07-25

|archive-url= https://web.archive.org/web/20070227214032/http://www.telly.org/86open/ |archive-date= 2007-02-27}}

FatELF is an ELF binary-format extension that adds fat binary capabilities.{{cite web|publisher=icculus.org| title=fatelf-specification v1| url=http://hg.icculus.org/icculus/fatelf/raw-file/tip/docs/fatelf-specification.txt| access-date=2010-07-25|last=Gordon| first=Ryan}} It is aimed for Linux and other Unix-like operating systems. Additionally to the CPU architecture abstraction (byte order, word size, CPU instruction set etc.), there is the potential advantage of software-platform abstraction e.g., binaries which support multiple kernel ABI versions. {{as of|2021}}, FatELF has not been integrated into the mainline Linux kernel.{{cite web|publisher=icculus.org| title=FatELF: Turns out I liked the uncertainty better| url=https://icculus.org/cgi-bin/finger/finger.pl?user=icculus&date=2009-11-03&time=19-08-04|access-date=2010-07-13|last=Gordon|first=Ryan}}{{cite web|publisher=osnews.com| title=Ryan Gordon Halts FatELF Project| url=https://www.osnews.com/story/22446/ryan-gordon-halts-fatelf-project|date=2009-11-03|access-date=2010-07-05|last=Holwerda|first=Thom}}{{cite web|url=https://lwn.net/Articles/392862/ |title=SELF: Anatomy of an (alleged) failure|publisher= Linux Weekly News|date= June 23, 2010|first=Joe|last=Brockmeier|access-date=2011-02-06}}

{{Portal|Computer programming}}

• Application binary interface
• Comparison of executable file formats
• DWARF{{snd}} a format for debugging data
• Intel Binary Compatibility Standard
• Portable Executable{{snd}} format used by Windows
• vDSO{{snd}} virtual DSO
• Position-independent code

{{Reflist|30em}}no

{{Div col|colwidth=30em}}

• {{cite book |author-last=Levine |author-first=John R. |author-link=John R. Levine |title=Linkers and Loaders |date=2000 |orig-year=October 1999 |edition=1 |publisher=Morgan Kaufmann |series=The Morgan Kaufmann Series in Software Engineering and Programming |location=San Francisco, USA |isbn=1-55860-496-0 |oclc=42413382 |url=https://www.iecc.com/linker/ |access-date=2020-01-12 |url-status=live |archive-url=https://archive.today/20121205032107/http://www.iecc.com/linker/ |archive-date=2012-12-05}} Code:https://archive.today/20200114225034/https://linker.iecc.com/code.html[ftp://ftp.iecc.com/pub/linker/]{{dead link|date=May 2025|bot=medic}}{{cbignore|bot=medic}} Errata: [https://linker.iecc.com/]
• Ulrich Drepper, How To Write Shared Libraries, Version 4.1.2 (2011). Published on the author's web page, https://www.akkadia.org/drepper.
• [https://web.archive.org/web/20070224140341/http://www-128.ibm.com/developerworks/power/library/pa-spec12/ An unsung hero: The hardworking ELF] by Peter Seebach, December 20, 2005, archived from the original on February 24, 2007
• {{webarchive|url=https://web.archive.org/web/20040225174057/http://developers.sun.com/solaris/articles/elf.html |title=LibElf and GElf – A Library to Manipulate ELf Files |date=February 25, 2004}}
• [https://www.linuxjournal.com/article/1059 The ELF Object File Format: Introduction], [https://www.linuxjournal.com/article/1060 The ELF Object File Format by Dissection] by Eric Youngdale (1995-05-01)
• [https://www.muppetlabs.com/~breadbox/software/tiny/teensy.html A Whirlwind Tutorial on Creating Really Teensy ELF Executables for Linux] by Brian Raiter
• [https://www.phrack.org/issues.html?issue=61&id=8#article ELF relocation into non-relocatable objects] by Julien Vanegue (2003-08-13)
• [https://www.phrack.org/issues.html?issue=63&id=9#article Embedded ELF debugging without ptrace] by the ELFsh team (2005-08-01)
• [https://netwinder.osuosl.org/users/p/patb/public_html/elf_relocs.html Study of ELF loading and relocs] by Pat Beirne (1999-08-03)

{{div col end}}

{{Div col|colwidth=30em}}

• [https://web.archive.org/web/20130403001804/http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/binary-formats.html FreeBSD Handbook: Binary formats] (archived version)
• [https://www.freebsd.org/cgi/man.cgi?query=elf&sektion=5 FreeBSD {{mono|elf(5)}} manual page]
• [https://www.netbsd.org/Documentation/elf.html NetBSD ELF FAQ]
• [https://man7.org/linux/man-pages/man5/elf.5.html Linux {{mono|elf(5)}} manual page]
• [https://docs.oracle.com/en/operating-systems/solaris/oracle-solaris/11.4/linkers-libraries/ Oracle Solaris Linker and Libraries Guide]
• [http://www.eresi-project.org/ The ERESI project: reverse engineering on ELF-based operating systems] {{Webarchive|url=https://web.archive.org/web/20210314190846/http://www.eresi-project.org/ |date=2021-03-14 }}
• [https://www.linuxtoday.com/developer/1999072600605PS Linux Today article on 86open] July 26, 1999
• [https://lists.debian.org/debian-announce/1997/msg00028.html Announcement of 86open on Debian Announce mailing list] October 10, 1997, Bruce Perens
• [https://www.groklaw.net/pdf/IBM-835-Exhibit_184.pdf Declaration of Ulrich Drepper (PDF)] in The SCO Group vs IBM, September 19, 2006
• [https://www.groklaw.net/articlebasic.php?story=20060813114048520 86open and ELF discussion] {{Webarchive|url=https://web.archive.org/web/20190201013659/http://www.groklaw.net/articlebasic.php?story=20060813114048520 |date=2019-02-01 }} on Groklaw, August 13, 2006

{{div col end}}

{{Executables}}

Category:Executable file formats