LDB toolchain generator gives you a working gcc-13 and clang-18 environment with cmake 3.29. It helps compiling modern C++ projects like ClickHouse and Doris on almost any Linux distros. ByConity is supported as well, but it requires manual adjustments due to its outdated toolchain support. The installation file can be found in Releases.
-
Download
ldb_toolchain_gen.shfrom Releases -
Execute the following command to generate LDB toolchain
bash ldb_toolchain_gen.sh /path/to/ldb_toolchain//path/to/ldb_toolchain/ is the directory where the toolchain is installed. The following directory structure will be created.
├── bin
├── include
├── lib
├── share
├── test
└── usr- Why do I still see version `GLIBC_xxx' not found?
It might be related to extern libc weak symbol such as this code. The root cause is related to how the linker processes symbols. The ideal solution is removing weak attribute from libc symbol declarations.
- Compiler/Linker doesn't work at all: Symbol not found in xxx.so?
Make sure LD_LIBRARY_PATH is not set.
Note The following content describes how
ldb_toolchain_gen.shis made. There is no need for common users to pay attention. It might lead to unnecessary confusion.
LDB toolchain generator helps generate toolchains derived from well-known linux distributions (LDB toolchain). LDB toolchain contains binaries from well-known linux distributions, which are heavily tested and optimized. It avoids the docker dependency which usually complicates developing workflows. Projects adopting LDB toolchain will likely generate byte-identical binaries. It benefits testing and debugging due to 100% consistency. It also lowers the bar of contributing code, as large C/C++ projects are usually daunting to build compared to Java, Golang, Rust, etc.
There are projects like Crosstool-NG and Gentoo-Prefix which aim at bootstraping toolchains from scratch. They are for advanced use cases and take a tremendous amount of time to bootstrap. It's also hard to control the quality of self-compiled toolchains.
There are projects like Exodus which can generate relocate Linux ELF binaries with wrappers and dependencies. Wrappers are usually good enough for common tools. However, toolchains like GCC and Clang relies heavily on /proc/self to re-exec the driver program multiple times, which will not work for ld-linux wrappers. As a result, we use patchelf to modify PT_INTERP and RPATH. Though RPATH can be relative to the binary's location, it's not possible to make a relocatable a.out that can tolerate changes to the absolute path of ld-linux. Thus, LDB toolchain generator requires user to specify a toolchain prefix.
The main branch illustrates how the generator assembles gcc-13 and clang-18 from ubuntu-18.04.
To actually generate the toolchain, the following steps can be used:
git clone https://github.com/amosbird/ldb_toolchain_gen
cd ldb_toolchain_gen
docker build . -t <your_toolchain_generator_tag> --network host
docker run --rm -v </path/to/store/toolchain>:/data <your_toolchain_generator_tag>
# Concrete Example
git clone https://github.com/amosbird/ldb_toolchain_gen
cd ldb_toolchain_gen
# You may need http proxy to overcome network errors during docker build
docker build . -t amosbird/some_toolchain_gen
# docker build --network host --build-arg http_proxy=http://127.0.0.1:10000 --build-arg https_proxy=http://127.0.0.1:10000 . -t amosbird/some_toolchain_gen
mkdir /tmp/some_toolchain_gen
# You may need root privilege
docker run --rm -v /tmp/some_toolchain_gen:/data amosbird/some_toolchain_gen
In the end, /tmp/some_toolchain_gen will contain a install script: ldb_toolchain_gen.sh.
The main branch is currently used to build ClickHouse and Doris.
If you want to generate a toolchain for the arm platform, you can change ARCH=x86_64 in the Dockerfile to ARCH=aarch64.
LDB toolchain might use newer libc which in turn will generate binaries that cannot be run on old host, even the same host for compilation. Users will encounter errors like version GLIBC_2.27 not found. A practical way of resolving this issue is described in this wiki.