Executable and Linkable Format
In computing, the Executable and Linkable Format, is a common standard file format for executable files, object code, shared libraries, and core dumps. First published in the specification for the application binary interface of the Unix operating system version named System V Release 4, and later in the Tool Interface Standard, it was quickly accepted among different vendors of Unix systems. In 1999, it was chosen as the standard binary file format for Unix and Unix-like systems on x86 processors by the 86open project.
By design, the ELF format is flexible, extensible, and cross-platform. For instance it supports different endiannesses and address sizes so it does not exclude any particular central processing unit or instruction set architecture. This has allowed it to be adopted by many different operating systems on many different hardware platforms.
File layout
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 header
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.Program header
The program header table tells the system how to create a process image. It is found at file offset e_phoff, and consists of e_phnum entries, each with size e_phentsize. The layout is slightly different in 32-bit ELF vs 64-bit ELF, because the p_flags are in a different structure location for alignment reasons. Each entry is structured as:Section header
Tools
-
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. -
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.Applications
Unix-like systems
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
- NetBSD
- OpenBSD
- Redox
- DragonFly BSD
- Syllable
- HP-UX
- QNX Neutrino
- MINIX
Non-Unix adoption
- OpenVMS, in its Itanium and amd64 versions
- BeOS Revision 4 and later for x86 based computers
- Haiku, an open source reimplementation of BeOS
- RISC OS
- Stratus VOS, in PA-RISC and x86 versions
- Windows 10 Anniversary Update using the Windows Subsystem for Linux.
- SkyOS
- Fuchsia OS
- Z/TPF
- HPE NonStop OS
- Deos
Game consoles
- PlayStation Portable, PlayStation Vita, PlayStation 2, PlayStation 3, PlayStation 4
- GP2X
- Dreamcast
- Gamecube
- Wii
- Wii U
PowerPC
- AmigaOS 4, the ELF executable has replaced the prior Extended Hunk Format which was used on Amigas equipped with PPC processor expansion cards.
- MorphOS
- AROS
Mobile phones
- Symbian OS v9 uses E32Image 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.
- 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 .so libraries for the Java Native Interface. With Android Runtime, the default since Android 5.0 "Lollipop", all applications are compiled into native ELF binaries on installation.
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.
Specifications
- Generic:
- * ' Edition 4.1
- * '
- AMD64:
- * '
- ARM:
- * '
- IA-32:
- * '
- IA-64:
- * '
- M32R:
- * ' Version 1.2
- MIPS:
- * '
- * '
- Motorola 6800:
- * '
- PA-RISC:
- * ' Version 1.43
- PowerPC:
- * '
- * 32-Bit Implementation
- * ' Version 1.9
- SPARC:
- * '
- S/390:
- * '
- zSeries:
- * '
- Symbian OS 9:
- *
86open
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. 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 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, 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 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 itself dissolved" on July 25, 1999.