How to Build ClickHouse on Linux 

Supported platforms:

  • x86_64
  • AArch64
  • Power9 (experimental)

Normal Build for Development on Ubuntu 

The following tutorial is based on the Ubuntu Linux system. With appropriate changes, it should also work on any other Linux distribution.

Install Git, CMake, Python and Ninja 

$ sudo apt-get install git cmake python ninja-build

Or cmake3 instead of cmake on older systems.

Install clang-13 (recommended) 

On Ubuntu/Debian you can use the automatic installation script (check official webpage)

sudo bash -c "$(wget -O -"

For other Linux distribution - check the availability of the prebuild packages or build clang from sources.

Use clang-13 for Builds 

$ export CC=clang-13
$ export CXX=clang++-13

Gcc can also be used though it is discouraged.

Checkout ClickHouse Sources 

$ git clone --recursive [email protected]:ClickHouse/ClickHouse.git


$ git clone --recursive

Build ClickHouse 

$ cd ClickHouse
$ mkdir build
$ cd build
$ cmake ..
$ ninja

To create an executable, run ninja clickhouse.
This will create the programs/clickhouse executable, which can be used with client or server arguments.

How to Build ClickHouse on Any Linux 

The build requires the following components:

  • Git (is used only to checkout the sources, it’s not needed for the build)
  • CMake 3.10 or newer
  • Ninja
  • C++ compiler: clang-11 or newer
  • Linker: lld
  • Python (is only used inside LLVM build and it is optional)

If all the components are installed, you may build in the same way as the steps above.

Example for Ubuntu Eoan:

sudo apt update
sudo apt install git cmake ninja-build clang++ python
git clone --recursive
mkdir build && cd build
cmake ../ClickHouse

Example for OpenSUSE Tumbleweed:

sudo zypper install git cmake ninja clang-c++ python lld
git clone --recursive
mkdir build && cd build
cmake ../ClickHouse

Example for Fedora Rawhide:

sudo yum update
yum --nogpg install git cmake make clang-c++ python3
git clone --recursive
mkdir build && cd build
cmake ../ClickHouse
make -j $(nproc)

How to Build ClickHouse Debian Package 

Install Git 

$ sudo apt-get update
$ sudo apt-get install git python debhelper lsb-release fakeroot sudo debian-archive-keyring debian-keyring

Checkout ClickHouse Sources 

$ git clone --recursive --branch master
$ cd ClickHouse

Run Release Script 

$ ./release

Faster builds for development 

Normally all tools of the ClickHouse bundle, such as clickhouse-server, clickhouse-client etc., are linked into a single static executable, clickhouse. This executable must be re-linked on every change, which might be slow. One common way to improve build time is to use the 'split' build configuration, which builds a separate binary for every tool, and further splits the code into several shared libraries. To enable this tweak, pass the following flags to cmake:


You Don’t Have to Build ClickHouse 

ClickHouse is available in pre-built binaries and packages. Binaries are portable and can be run on any Linux flavour.

They are built for stable, prestable and testing releases as long as for every commit to master and for every pull request.

To find the freshest build from master, go to commits page, click on the first green checkmark or red cross near commit, and click to the “Details” link right after “ClickHouse Build Check”.

Split build configuration 

Normally ClickHouse is statically linked into a single static clickhouse binary with minimal dependencies. This is convenient for distribution, but it means that on every change the entire binary is linked again, which is slow and may be inconvenient for development. There is an alternative configuration which creates dynamically loaded shared libraries instead, allowing faster incremental builds. To use it, add the following flags to your cmake invocation:


Note that the split build has several drawbacks: * There is no single clickhouse binary, and you have to run clickhouse-server, clickhouse-client, etc. * Risk of segfault if you run any of the programs while rebuilding the project. * You cannot run the integration tests since they only work a single complete binary. * You can't easily copy the binaries elsewhere. Instead of moving a single binary you'll need to copy all binaries and libraries.

Rating: 4.2 - 15 votes

Was this content helpful?