Arch Linux User Repository

After the long discussion in dev-group of Telegram, the most straight forward way to use clickhouse is the usage of the official build.

Also building with persistent ccache could noticeably speed up subsequent builds.

rbelio, you have several options:

1. Try to find out where your resources are wasted and utilize them better. It could be slow disk I/O, slow filesystem (check fs mount options), only one core used (check MAKEFLAGS in /etc/makepkg.conf). Sometimes installing "ninja" helps to build ClickHouse faster.

2. Build the package on a faster box, then transfer the binary. Or use some distributed tools, like distcc or dist-clang.

3. Do not apply full system updates too often to avoid frequent rebuilds. However this means taking risk of broken packages and introducing security vulnerabilities.

4. (Not recommended.) You can hack your binary to point to another library with patchelf --replace-needed. Anything could break after this hack but sometimes it would work. Maybe this is an acceptable use case for non-production environments.

kmeaw, thanks. I have another question, is there a way to mitigate the long compilation time everytime the libraries get updated? It takes me at least a couple of hours of compilation (over i7 dell laptop with ssd and 16gb). After reading more about arch I finally understood that partial update is not allowed and old libraries are always deleted when new libraries are available to the package manager.

rbelio, you cannot just link to a libicuuc.so instead of a libicuuc.so.62, because ".62" is there for a reason: the SONAME field value is "libiccuc.so.62", which means that anything else like "libiccuc.so.61" is not ABI-compatible with libiccuc.so.62. Everytime the SONAME is changed, you need to rebuild all the binaries depending on it. You can use something similar to Gentoo's revdep-rebuild to automate the process.

There is a constant issue when libraries get upgraded and clickhouse stays behind. depending for example on libicuuc.so.62 can you please make sure it will depend on libicuuc.so without the explicit version number. thanks. P.S libicuuc is not the only library there are several ones.

ext, building clickhouse with ninja installed has been fixed.

Arhangel64, it seems that you have updated your double-conversion library (from 1.x to 3.x) without rebuilding clickhouse package. zlib-ng issue is fixed in pkgrel=2.

/usr/bin/clickhouse-server: error while loading shared libraries: libdouble-conversion.so.1: cannot open shared object file: No such file or directory

could you please try it before publishing?

I'm not sure about this zlib-ng, may be it's already in some other package, but i got to compile it myself.

https://github.com/Dead2/zlib-ng

First you compile, you "# make install", then you edit your /usr/lib/systemd/system/clickhouse-server.service appending Environment="LD_PRELOAD=/usr/local/lib/libz-ng.so.1" there Then it works.

Is there a way just to package it properly? Is there a way to use system libraries?

/usr/bin/clickhouse-server: error while loading shared libraries: libz-ng.so.1: cannot open shared object file: No such file or directory