Install gcc@13 with Homebrew, apt, MacPorts, zypper, apk, dnf, Nix, pacman, scoop

Project links

• Homepage
• Repository
• Upstream docs
• Package manager page

Commands and aliases

• aarch64-apple-darwin24-c++-13
• aarch64-apple-darwin24-g++-13
• aarch64-apple-darwin24-gcc-13
• aarch64-apple-darwin24-gcc-ar-13
• aarch64-apple-darwin24-gcc-nm-13
• aarch64-apple-darwin24-gcc-ranlib-13
• aarch64-apple-darwin24-gfortran-13
• c++-13
• cpp-13
• g++-13
• gcc-13
• gcc-ar-13
• gcc-nm-13
• gcc-ranlib-13
• gcov-13
• gcov-dump-13
• gcov-tool-13
• gfortran-13
• lto-dump-13

Project history

GCC began as the GNU C Compiler. The GCC project history records the first beta release on March 22, 1987, by Richard Stallman, originally for the GNU operating system and initially centered on C.

During the 1990s, GCC grew beyond C into a multi-language compiler suite. The official GCC 2.95 page notes that the name changed from GNU C Compiler to GNU Compiler Collection because the compiler supported several languages beyond C.

A major governance and development milestone was the EGCS fork in 1997, created to merge active GCC development work from several communities. GCC and EGCS were reunified in April 1999, and GCC 2.95 was the first release after that reunification.

Adoption history

GCC became widely adopted because it was both the GNU system compiler and an openly developed, portable optimizing compiler. The current mission statement emphasizes support for many platforms, many architectures, open mailing lists, and participation by individuals and companies.

The GCC 13 package represents package-manager demand for a stable major compiler series rather than only the newest compiler. Official release branches and tags make these major lines easy for distributors and users to pin, audit, and rebuild.

How it is used

As packaged here, GCC 13 exposes version-suffixed compiler tools such as gcc-13, g++-13, cpp-13, gcov-13, and gfortran-13, depending on the platform package. This lets users select the intended compiler line explicitly in build scripts.

Official GCC installation documentation covers downloading sources, configuring, building, testing, and final installation, while the online manuals document compiler invocation, language front ends, runtime libraries, and toolchain options.

The GCC 13 change notes include toolchain-facing features such as SARIF diagnostic output, LTO jobserver improvements, and C/C++ warning and analyzer work.

Why package nerds care

Versioned GCC packages matter because compilers are infrastructure, not leaf applications. A build may need a particular major GCC for language support, libstdc++ behavior, Fortran ABI expectations, sanitizer behavior, or target support, while another project on the same machine needs a different line.

The official Git repository page documents release branches and release tags, which is exactly the provenance package maintainers need when mapping formula names such as gcc@12 or gcc@15 to upstream source history.

Timeline

• 1987: First GCC beta release as the GNU C Compiler
• 1997: EGCS fork announced as an experimental GCC development project
• 1999: GCC and EGCS reunified; GCC 2.95 released after reunification
• 2023: GCC 13.1 released on April 26
• 2025: GCC 13.4 released on June 5

Related projects

• EGCS is the historically important GCC fork that was later reunified with GCC.
• Related components within the GCC distribution include libstdc++, GFortran, GOMP/libgomp, GCC Go, GDC, GM2, and newer front ends documented on the official GCC site.
• GCC is part of the wider GNU toolchain ecosystem and is commonly used with source-control, build, and generated-file tooling such as Git, Autoconf, Bison, Automake, Xgettext, and Gperf, all mentioned in GCC source-tree documentation.

Sources

• https://gcc.gnu.org/
• https://gcc.gnu.org/gcc-13/changes.html
• https://gcc.gnu.org/gccmission.html
• https://gcc.gnu.org/git.html
• https://gcc.gnu.org/releases.html
• https://gcc.gnu.org/wiki/History