xPack MinGW-w64 GCC v12.2.0-1 released
The xPack MinGW-w64 GCC is a standalone cross-platform binary distribution of Mingw-w64 GCC.
There are separate binaries for Windows (Intel 64-bit), macOS (Intel 64-bit, Apple Silicon 64-bit) and GNU/Linux (Intel 64-bit, Arm 32/64-bit).
The binary files are available from GitHub Releases.
- GNU/Linux Intel 64-bit: any system with GLIBC 2.27 or higher (like Ubuntu 18 or later, Debian 10 or later, RedHat 8 later, Fedora 29 or later, etc)
- GNU/Linux Arm 32/64-bit: any system with GLIBC 2.27 or higher (like Raspberry Pi OS, Ubuntu 18 or later, Debian 10 or later, RedHat 8 later, Fedora 29 or later, etc)
- Intel Windows 64-bit: Windows 7 with the Universal C Runtime (UCRT), Windows 8, Windows 10
- Intel macOS 64-bit: 10.13 or later
- Apple Silicon macOS 64-bit: 11.6 or later
The full details of installing the xPack MinGW-w64 GCC on various platforms are presented in the separate Install page.
The easiest way to install GCC is with
by using the binary xPack, available as
xpm tool available, installing
the latest version of the package and adding it as
a dependency for a project is quite easy:
cd my-project xpm init # Only at first use. xpm install @xpack-dev-tools/mingw-w64-gcc@latest ls -l xpacks/.bin
To install this specific version, use:
xpm install @email@example.com
It is also possible to install Meson Build globally, in the user home folder, but this requires xPack aware tools to automatically identify them and manage paths.
xpm install --global @xpack-dev-tools/mingw-w64-gcc@latest --verbose
To remove the links created by xpm in the current project:
cd my-project xpm uninstall @xpack-dev-tools/mingw-w64-gcc
To completely remove the package from the global store:
xpm uninstall --global @xpack-dev-tools/mingw-w64-gcc
The xPack MinGW-w64 GCC generally follows the official GCC releases.
The current version is based on:
- GCC version 12.2.0 from August 19, 2022;
- binutils version 2.39 from Aug 5, 2022
- MinGW-w64 version 10.0.0
The supported languages are:
Note: Obj-C/C++ support is minimalistic.
Compared to the upstream, there are no functional changes.
On all platforms the packages are standalone, and expect only the standard runtime to be present on the host.
All dependencies that are build as shared libraries are copied locally
libexec folder (or in the same folder as the executable for Windows).
To avoid issues with DLLs, specific when using toolchains installed in custom locations, it is highly recommended to use only the static versions of the GCC libraries.
For C programs, append
-static-libgcc to the linker line.
For C++ programs, since the toolchain is configured to use POSIX threads,
-static-libstdc++, use the more explicit variant
-Wl,-Bstatic,-lstdc++,-lpthread,-Bdynamic when invoking the linker.
On GNU/Linux the binaries are adjusted to use a relative path:
$ readelf -d library.so | grep runpath 0x000000000000001d (RPATH) Library rpath: [$ORIGIN]
In the GNU ld.so search strategy, the
the highest priority, higher than
LD_LIBRARY_PATH, so if this later one
is set in the environment, it should not interfere with the xPack binaries.
Please note that previous versions, up to mid-2020, used
has a priority lower than
LD_LIBRARY_PATH, and does not tolerate setting
it in the environment.
Similarly, on macOS, the binaries are adjusted with
install_name_tool to use a
To save space and bandwidth, the original GNU GCC documentation is available online.
The binaries for all supported platforms (Windows, macOS and GNU/Linux) were built using the xPack Build Box (XBB), a set of build environments based on slightly older distributions, that should be compatible with most recent systems.
The scripts used to build this distribution are in:
For the prerequisites and more details on the build procedure, please see the README-MAINTAINER page.
Before publishing, a set of simple tests were performed on an exhaustive set of platforms. The results are available from:
The binaries were tested on a variety of platforms, but mainly to check the integrity of the build, not the compiler functionality.
The SHA-256 hashes for the files are:
664e753fcd9686e5bdfb73990a7815654c4dbf232877c92bab8a0e8e94a8d211 xpack-mingw-w64-gcc-12.2.0-1-darwin-arm64.tar.gz 6f02e88ab347b1d3383602b8e3182bfbca494bbe9e3228cddbb3a5e9a864bf8a xpack-mingw-w64-gcc-12.2.0-1-darwin-x64.tar.gz 391bd92154544ef84c129f2b8dab912168f0d9b5efa5ff9a8029eecafb3f33e2 xpack-mingw-w64-gcc-12.2.0-1-linux-arm.tar.gz 739d788976afbeaf903dac92344a715b3d4a0703fc0f7dd97eeec1f0b56588d5 xpack-mingw-w64-gcc-12.2.0-1-linux-arm64.tar.gz 524af0b208b5052da55e109525e0f57788002df7e6a7a4088d44908dea746a2d xpack-mingw-w64-gcc-12.2.0-1-linux-x64.tar.gz 43ca4e249941d335047a874ba3ff7d610912b004d805417b6340f4ed26132567 xpack-mingw-w64-gcc-12.2.0-1-win32-x64.zip
Support for 32-bit Intel Linux and Intel Windows was dropped in 2022. Support for 32-bit Arm Linux (armv7l) will be preserved for a while, due to the large user base of 32-bit Raspberry Pi systems.
Linux minimum requirements
Support for RedHat 7 was dropped in 2022 and the minimum requirement was raised to GLIBC 2.27, available starting with Ubuntu 18, Debian 10 and RedHat 8.
- GitHub xpack-dev-tools/mingw-w64-gcc-xpack
- this release
- all xPack releases
- individual file counters (grouped per release)
- npmjs.com @xpack-dev-tools/mingw-w64-gcc
Credit to Shields IO for the badges and to Somsubhra/github-release-stats for the individual file counters.