ELFEDIT(1)

💖 ELFEDIT(1) 💖

okay bestie, gather round, because this is the elfedit page from the GNU Development Tools collection and it's genuinely iconic. it updates the ELF header and program property of ELF files. yes. that ELF. no cap.

---

✨ NAME ✨

elfedit — update ELF header and program property of ELF files

---

🌸 SYNOPSIS 🌸

elfedit [--input-mach=machine]
        [--input-type=type]
        [--input-osabi=osabi]
        [--input-abiversion=version]
        --output-mach=machine
        --output-type=type
        --output-osabi=osabi
        --output-abiversion=version
        --enable-x86-feature=feature
        --disable-x86-feature=feature
        [-v|--version]
        [-h|--help]
        elffile...

---

🦋 DESCRIPTION 🦋

so like, elfedit updates the ELF header and the program property of ELF files — but only the ones that have the matching ELF machine and file types, okay? the options are what control how and which fields in the ELF header and program property get updated. it's giving ✨surgical✨.

elffile... — those are the ELF files you wanna update. and the range?? 32-bit AND 64-bit ELF files are supported, bestie. plus archives containing ELF files. versatility, we love her. 👑

---

💅 OPTIONS 💅

the long and short forms of options, shown here as alternatives, are equivalent. and listen — at least one of the --output-mach, --output-type, --output-osabi, --output-abiversion, --enable-x86-feature and --disable-x86-feature options must be given. like, you can't just show up empty-handed. this is a party, not a vibe check. 🙈

• --input-mach=machine — sets the matching input ELF machine type to machine. if --input-mach isn't specified, it'll match any ELF machine types. no pickiness, she's flexible.
  • the supported ELF machine types are i386, IAMCU, L1OM, K1OM and x86-64. 💖
• --output-mach=machine — changes the ELF machine type in the ELF header to machine. the supported ELF machine types are the same as --input-mach, iykyk.
• --input-type=type — sets the matching input ELF file type to type. if --input-type isn't specified, it'll match any ELF file types. chill like that.
  • the supported ELF file types are rel, exec and dyn. 🌈
• --output-type=type — changes the ELF file type in the ELF header to type. the supported ELF types are the same as --input-type.
• --input-osabi=osabi — sets the matching input ELF file OSABI to osabi. if --input-osabi isn't specified, it'll match any ELF OSABIs.
  • the supported ELF OSABIs are none, HPUX, NetBSD, GNU, Linux (alias for GNU), Solaris, AIX, Irix, FreeBSD, TRU64, Modesto, OpenBSD, OpenVMS, NSK, AROS and FenixOS. look at that roster. main character energy for real. ⭐
• --output-osabi=osabi — changes the ELF OSABI in the ELF header to osabi. the supported ELF OSABI are the same as --input-osabi.
• --input-abiversion=version — sets the matching input ELF file ABIVERSION to version. version must be between 0 and 255. if --input-abiversion isn't specified, it'll match any ELF ABIVERSIONs.
• --output-abiversion=version — changes the ELF ABIVERSION in the ELF header to version. version must be between 0 and 255.
• --enable-x86-feature=feature — sets the feature bit in program property in exec or dyn ELF files with machine types of i386 or x86-64. the supported features are ibt, shstk, lam_u48 and lam_u57. turning it ON, slay. 🔥
• --disable-x86-feature=feature — clears the feature bit in program property in exec or dyn ELF files with machine types of i386 or x86-64. the supported features are the same as --enable-x86-feature. turning it OFF, also valid. 💀

note: --enable-x86-feature and --disable-x86-feature are available only on hosts with mmap support. if your host doesn't have it, these two are simply not invited to the function. 😭

• -v, --version — displays the version number of elfedit. like, who even are you? 💁
• -h, --help — displays the command-line options understood by elfedit. the little menu of dreams.
• @file — reads command-line options from file. the options read are inserted in place of the original @file option. if file does not exist, or cannot be read, then the option will be treated literally, and not removed. (so it just kinda sits there. iconic behaviour honestly.)
  • options in file are separated by whitespace. a whitespace character may be included in an option by surrounding the entire option in either single or double quotes. any character (including a backslash) may be included by prefixing the character to be included with a backslash. the file may itself contain additional @file options; any such options will be processed recursively. yes bestie, it's giving inception. 🌀

---

🎀 SEE ALSO 🎀

• readelf(1), and the Info entries for binutils.

---

👑 COPYRIGHT 👑

Copyright (c) 1991-2026 Free Software Foundation, Inc.

Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, with no Front-Cover Texts, and with no Back-Cover Texts. A copy of the license is included in the section entitled "GNU Free Documentation License".

---

and that's the whole page, bestie!! this one came from binutils-2.46.1, dated 2026-09-07 — go forth and edit those ELF headers, you absolute legend. 🫶💜✨