Install m68k-elf-gcc with Homebrew, MacPorts

Project links

• Homepage

Commands and aliases

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

Project history

GCC began as the GNU system's compiler and grew into the GNU Compiler Collection. The current project includes front ends for many languages and runtime libraries, and it is developed as free software under the GNU Project.

The `m68k-elf-gcc` package is a target build of upstream GCC rather than an independent compiler project. Its executables are prefixed with `m68k-elf-` so they can live beside the host compiler and other cross compilers.

GCC's official documentation includes M680x0 and ColdFire target options for generating and tuning code for processors such as 68000, 68010, 68020, 68030, 68040, 68060, CPU32, and ColdFire families.

Adoption history

GCC is widely adopted because it targets many architectures and supports both native and cross compilation. The GCC mission statement explicitly calls out multiple architectures, diverse environments, new targets, and an open development model.

The supplied package facts show Homebrew and MacPorts packages for `m68k-elf-gcc`, placing it in the small but important family of retrocomputing, embedded, and bare-metal cross compilers available through desktop package managers.

How it is used

The GCC manual describes the usual executable as `gcc`, `machine-gcc` when cross-compiling, or `machine-gcc-version` for a versioned driver. This package follows that convention with commands such as `m68k-elf-gcc`, `m68k-elf-g++`, `m68k-elf-cpp`, and related GCC helper tools.

Developers use it with `m68k-elf-binutils` to compile C and C++ code, assemble generated output, and link ELF binaries for bare-metal 68k targets. Target options such as `-march`, `-mcpu`, `-mtune`, `-m68000`, and `-m68020-60` control generated code for different 680x0 and ColdFire variants.

Why package nerds care

Cross-GCC packages are more than a compiler binary: they encode a target triplet, ABI assumptions, binutils pairing, runtime-library choices, and build-system expectations.

For package maintainers, `m68k-elf-gcc` is notable because it makes a non-host architecture feel native to build systems while keeping all tools target-prefixed and isolated from the host GCC or Clang.

Timeline

• 1987: GCC first emerged as the GNU C Compiler era began
• 2024: GCC mission statement page documents open development, multiple architectures, and new targets
• 2026: GCC 16.1 listed as a supported release on the official GCC site
• 2026: Homebrew package facts list GCC 16.1.0 target-prefixed m68k-elf executables

Related projects

• m68k-elf-binutils supplies the matching assembler, linker, and object utilities.
• GNU Binutils, GNU Make, and Autoconf-era build systems are common neighbors in source builds using GCC cross compilers.
• Other GCC cross packages follow the same target-triplet executable convention.

Sources

• https://gcc.gnu.org/
• https://gcc.gnu.org/gccmission.html
• https://gcc.gnu.org/git.html
• https://gcc.gnu.org/onlinedocs/
• https://gcc.gnu.org/onlinedocs/gcc/Invoking-GCC.html
• https://gcc.gnu.org/onlinedocs/gcc/M680x0-Options.html
• source_facts.executables
• source_facts.package-manager