Install x86_64-elf-gcc with Homebrew, MacPorts

Project links

• Homepage
• Repository
• Upstream docs
• Package manager page

Commands and aliases

• x86_64-elf-c++
• x86_64-elf-cpp
• x86_64-elf-g++
• x86_64-elf-gcc
• x86_64-elf-gcc-16.1.0
• x86_64-elf-gcc-ar
• x86_64-elf-gcc-nm
• x86_64-elf-gcc-ranlib
• x86_64-elf-gcov
• x86_64-elf-gcov-dump
• x86_64-elf-gcov-tool
• x86_64-elf-lto-dump

Project history

GCC began as the GNU C Compiler, written for the GNU operating system and first released in 1987. It later expanded into the GNU Compiler Collection, with official front ends for C, C++, Objective-C, Objective-C++, Fortran, Ada, Go, D, Modula-2, COBOL, Rust, Algol 68, and related runtime libraries documented by the GCC project.

The GCC governance and release story also matters to cross packages. GCC's 2.95 release in July 1999 was the first after the GCC/EGCS reunification, and the project has since been maintained by a global developer community under a steering committee. The modern GCC site emphasizes regular releases that work across native and cross targets.

Adoption history

Cross compilation has been central to GCC's identity because GCC supports many processors and systems. The official GCC homepage explicitly says the project aims for releases that work on a variety of native and cross targets, while OSDev documentation explains why hobby OS and kernel developers build target-specific GCCs instead of relying on the host compiler.

For `x86_64-elf`, adoption is concentrated in OSDev and freestanding x86-64 work. The target prefix lets build systems call `x86_64-elf-gcc` and get code-generation defaults for x86-64 ELF rather than the host triple. OSDev guidance also notes that a target-specific compiler removes the need to pass host-overriding options such as `-m64` for every build.

How it is used

Typical users compile freestanding C or C++ with options such as `-ffreestanding`, link with a custom linker script, and provide their own runtime entry point instead of relying on a hosted C library. The compiler may also be used as the driver for assembly and linking so it selects the matching target Binutils tools.

In kernel work, x86-64 has hardware and ABI details that package users must understand beyond simply choosing this compiler. OSDev material commonly calls out issues such as separate 32-bit and 64-bit toolchains, bootloader expectations, and x86-64 red-zone behavior; the package gives the target compiler, but the build still has to define the freestanding environment correctly.

Why package nerds care

x86_64-elf-gcc is important because it packages the first serious bootstrap hurdle of hobby OS development. Instead of every user manually building a cross GCC, the package provides a stable prefixed compiler that can be dropped into Makefiles and tutorials.

It is also a clear example of how package names can describe configuration rather than upstream identity. The upstream is GCC; the meaningful package distinction is the target triple, which changes what the compiler assumes about object format, runtime, and operating-system services.

Timeline

• 1987-03-22: GCC 1.0 is first released as the GNU C Compiler.
• 1999-04: The EGCS steering committee is appointed as the official GCC maintainer after the GCC/EGCS reunification process.
• 1999-07-31: GCC 2.95 is released as the first GCC release after GCC/EGCS reunification.
• 2000s: OSDev communities popularize target-prefixed GCC cross compilers such as `i686-elf-gcc` and later `x86_64-elf-gcc` for freestanding kernels.
• 2026-04-30: GCC 16.1 is released, and the GCC homepage lists ongoing support for native and cross targets.

Related projects

• GNU Binutils provides the assembler, linker, and object tools required by a matching `x86_64-elf` GCC toolchain.
• GDB is commonly built as a target-aware debugger alongside cross GCC and Binutils.
• Newlib and other small C libraries are used when a freestanding cross compiler grows into a hosted embedded or OS-specific toolchain.
• LLVM/Clang can also target freestanding x86-64 ELF workflows, often with `lld` and LLVM binary tools.

Sources

• https://gcc.gnu.org/
• https://gcc.gnu.org/gcc-2.95/
• https://gcc.gnu.org/onlinedocs/
• https://gcc.gnu.org/releases.html
• https://gcc.gnu.org/steering.html
• https://wiki.osdev.org/Bare_Bones
• https://wiki.osdev.org/GCC_Cross-Compiler
• https://wiki.osdev.org/Why_do_I_need_a_Cross_Compiler%3F