Version 13.0.1-1 is a new release; it follows the upstream release.

The xPack LLVM clang is a standalone cross-platform binary distribution of LLVM clang.

There are separate binaries for Windows (x64), macOS (x64, arm64) and GNU/Linux (x64, arm64 and arm).

Download

The binary files are available from GitHub Releases.

Prerequisites

  • x64 GNU/Linux: any system with GLIBC 2.27 or higher (like Ubuntu 18 or later, Debian 10 or later, RedHat 8 or later, Fedora 29 or later, etc)
  • arm64/arm GNU/Linux: any system with GLIBC 2.27 or higher (like Raspberry Pi OS, Ubuntu 18 or later, Debian 10 or later, RedHat 8 or later, Fedora 29 or later, etc)
  • x64 Windows: Windows 7 with the Universal C Runtime (UCRT), Windows 8, Windows 10
  • x64 macOS: 10.13 or later
  • arm64 macOS: 11.6 or later

Install

The full details of installing the xPack LLVM clang on various platforms are presented in the separate Install page.

Easy install

The easiest way to install LLVM clang is with xpm by using the binary xPack, available as @xpack-dev-tools/clang from the npmjs.com registry.

With the 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/clang@latest

ls -l xpacks/.bin

To install this specific version, use:

xpm install @xpack-dev-tools/clang@13.0.1-1.1

It is also possible to install LLVM clang 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/clang@latest --verbose

Uninstall

To remove the links from the current project:

cd my-project

xpm uninstall @xpack-dev-tools/clang

To completely remove the package from the central xPacks store:

xpm uninstall --global @xpack-dev-tools/clang

Compliance

The xPack LLVM clang generally follows the official LLVM clang releases.

The current version is based on:

  • LLVM clang version 13.0.1, from Feb 2nd, 2022.

Changes

Compared to the upstream, there are no functional changes.

Bug fixes

  • none

Enhancements

  • to support machines where only the Command Line Tools are installed, the /Library/Developer/CommandLineTools/usr/include/c++/v1 folder is also added to the header search path.

Known problems

  • on GNU/Linux, support for the clang run-time and C++ libraries is basic, the libraries are available, but using them is tricky, since it requires the compiled binaries to take care of the path to them, otherwise it is very likely that the system libraries will be used; thus it is recommended to avoid such use cases.
  • on macOS, the /Library/Developer/CommandLineTools/usr/include/c++/v1 was added to the include path; unfortunately this may crash some builds; removed in 15.0.7-3
  • when clang is invoked via a link from a different folder, the InstalledDir does not reflect the correct install folder, and the new clang system headers are either not found or the host system headers are used; fixed in 15.0.7-4

Shared libraries

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 in the libexec folder (or in the same folder as the executable for Windows).

DT_RPATH and LD_LIBRARY_PATH

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 DT_RPATH has 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 DT_RUNPATH, which has a priority lower than LD_LIBRARY_PATH, and does not tolerate setting it in the environment.

@rpath and @loader_path

Similarly, on macOS, the binaries are adjusted with install_name_tool to use a relative path.

Documentation

To save space and bandwidth, the original documentation is available online.

Build

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:

  • distro-info/scripts

For the prerequisites and more details on the build procedure, please see the README-MAINTAINER page.

CI tests

Before publishing, a set of simple tests were performed on an exhaustive set of platforms. The results are available from:

Tests

The binaries were tested on a variety of platforms, but mainly to check the integrity of the build, not the compiler functionality.

Checksums

The SHA-256 hashes for the files are:

f22c74222f536b69f1315a1d1774077faf2cfb506a04fe0d39ceee5a7e748cda
xpack-clang-13.0.1-1-darwin-arm64.tar.gz

95a3324a8beea2c22b206f1de4832a4c2eccb10b005a19e3ef0201447cd6ad3e
xpack-clang-13.0.1-1-darwin-x64.tar.gz

9680d353e68ac5195b386c905c561403404a714432e225b9774a54ff04223127
xpack-clang-13.0.1-1-linux-arm.tar.gz

01d694decc6e3603b6675c4e55a18dfe833babe364151f087823e578f8dd8d83
xpack-clang-13.0.1-1-linux-arm64.tar.gz

36ed757719f3de422eee0d44a2e43d01cdc710783ea77d8c54a11cc6ca353e7e
xpack-clang-13.0.1-1-linux-x64.tar.gz

7dfb1102eb981139684adcb3ba4396dcb6e3c6450f7ce9a90a556f6871c58ef0
xpack-clang-13.0.1-1-win32-x64.zip

Deprecation notices

32-bit support

Support for 32-bit x86 GNU/Linux and x86 Windows was dropped in 2022. Support for 32-bit Arm GNU/Linux will be preserved for a while, due to the large user base of 32-bit Raspberry Pi systems.

GNU/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.

Download analytics

Credit to Shields IO for the badges and to Somsubhra/github-release-stats for the individual file counters.