Some notes on how to build Qtum Core in Unix.
(For BSD specific instructions, see build-*bsd.md in this directory.)
Always use absolute paths to configure and compile Qtum Core and the dependencies. For example, when specifying the path of the dependency:
../dist/configure --enable-cxx --disable-shared --with-pic --prefix=$BDB_PREFIX
Here BDB_PREFIX must be an absolute path - it is defined using $(pwd) which ensures the usage of the absolute path.
./autogen.sh
./configure
make # use "-j N" for N parallel jobs
make install # optionalThis will build qtum-qt as well, if the dependencies are met.
See dependencies.md for a complete overview.
C++ compilers are memory-hungry. It is recommended to have at least 1.5 GB of memory available when compiling Qtum Core. On systems with less, gcc can be tuned to conserve memory with additional CXXFLAGS:
./configure CXXFLAGS="--param ggc-min-expand=1 --param ggc-min-heapsize=32768"
Alternatively, or in addition, debugging information can be skipped for compilation. The default compile flags are
-g -O2, and can be changed with:
./configure CXXFLAGS="-O2"
Finally, clang (often less resource hungry) can be used instead of gcc, which is used by default:
./configure CXX=clang++ CC=clang
Build requirements:
sudo apt-get install build-essential libtool autotools-dev automake pkg-config bsdmainutils python3 libgmp3-dev
Now, you can either build from self-compiled depends or install the required dependencies:
sudo apt-get install libevent-dev libboost-dev
SQLite is required for the descriptor wallet:
sudo apt install libsqlite3-dev
Berkeley DB is required for the legacy wallet. Ubuntu and Debian have their own libdb-dev and libdb++-dev packages,
but these will install Berkeley DB 5.1 or later. This will break binary wallet compatibility with the distributed
executables, which are based on BerkeleyDB 4.8. If you do not care about wallet compatibility, pass
--with-incompatible-bdb to configure. Otherwise, you can build Berkeley DB yourself.
To build Qtum Core without wallet, see Disable-wallet mode
Optional port mapping libraries (see: --with-miniupnpc and --with-natpmp):
sudo apt install libminiupnpc-dev libnatpmp-dev
ZMQ dependencies (provides ZMQ API):
sudo apt-get install libzmq3-dev
User-Space, Statically Defined Tracing (USDT) dependencies:
sudo apt install systemtap-sdt-dev
GUI dependencies:
If you want to build qtum-qt, make sure that the required packages for Qt development
are installed. Qt 5 is necessary to build the GUI.
To build without GUI pass --without-gui.
To build with Qt 5 you need the following:
sudo apt-get install libqt5gui5 libqt5core5a libqt5dbus5 qttools5-dev qttools5-dev-tools
Additionally, to support Wayland protocol for modern desktop environments:
sudo apt install qtwayland5
libqrencode (optional) can be installed with:
sudo apt-get install libqrencode-dev
Once these are installed, they will be found by configure and a qtum-qt executable will be built by default.
Build requirements:
sudo dnf install gcc-c++ libtool make autoconf automake python3 gmp-devel
Now, you can either build from self-compiled depends or install the required dependencies:
sudo dnf install libevent-devel boost-devel
SQLite is required for the descriptor wallet:
sudo dnf install sqlite-devel
Berkeley DB is required for the legacy wallet:
sudo dnf install libdb4-devel libdb4-cxx-devel
Newer Fedora releases, since Fedora 33, have only libdb-devel and libdb-cxx-devel packages, but these will install
Berkeley DB 5.3 or later. This will break binary wallet compatibility with the distributed executables, which
are based on Berkeley DB 4.8. If you do not care about wallet compatibility,
pass --with-incompatible-bdb to configure. Otherwise, you can build Berkeley DB yourself.
To build Qtum Core without wallet, see Disable-wallet mode
Optional port mapping libraries (see: --with-miniupnpc and --with-natpmp):
sudo dnf install miniupnpc-devel libnatpmp-devel
ZMQ dependencies (provides ZMQ API):
sudo dnf install zeromq-devel
User-Space, Statically Defined Tracing (USDT) dependencies:
sudo dnf install systemtap
GUI dependencies:
If you want to build qtum-qt, make sure that the required packages for Qt development
are installed. Qt 5 is necessary to build the GUI.
To build without GUI pass --without-gui.
To build with Qt 5 you need the following:
sudo dnf install qt5-qttools-devel qt5-qtbase-devel
Additionally, to support Wayland protocol for modern desktop environments:
sudo dnf install qt5-qtwayland
libqrencode (optional) can be installed with:
sudo dnf install qrencode-devel
Once these are installed, they will be found by configure and a qtum-qt executable will be built by default.
You need to build boost manually, and if it's not in standard library paths, you need to add /path/to/boost/lib into LD_LIBRARY_PATH env when building Qtum.
Build requirements:
sudo yum install epel-release
sudo yum install gcc-c++ libtool libdb4-cxx-devel openssl-devel libevent-devel gmp-devel
To build with Qt 5 (recommended) you need the following:
sudo yum install qt5-qttools-devel protobuf-devel qrencode-devel
Build requirements:
./qtum/contrib/script/setup-ubuntu16.sh
Build Qtum:
cd qtum/contrib/script
./build-qtum-linux.sh -j2
The home folder for the installation package need to be qtum/contrib/script.
After the build finish, the installation package is present into qtum/contrib/script.
Installation package example: qtum-22.1-x86_64-pc-linux-gnu.tar.gz
The package has the following dependencies when used on Ubuntu 16 machine that is not used for building Qtum:
qtum-qt require libxcb-xinerama0 to be installed on Ubuntu 16 (both 32 and 64 bit versions):
sudo apt-get install libxcb-xinerama0 -y
Qtum require GCC 7 standard library be installed for Ubuntu 16 only on 32 bit version:
sudo add-apt-repository ppa:ubuntu-toolchain-r/test
sudo apt-get update
sudo apt-get install gcc-7 g++-7 -y
Build requirements:
su
./qtum/contrib/script/setup-centos7.sh
The operating system might restart after finish with installing the build requirements.
Build Qtum:
cd qtum/contrib/script
./build-qtum-linux.sh -j2
The home folder for the installation package need to be qtum/contrib/script.
After the build finish, the installation package is present into qtum/contrib/script.
Installation package example: qtum-22.1-x86_64-pc-linux-gnu.tar.gz
The release is built with GCC and then "strip qtumd" to strip the debug symbols, which reduces the executable size by about 90%.
miniupnpc may be used for UPnP port mapping. It can be downloaded from here. UPnP support is compiled in and turned off by default.
libnatpmp may be used for NAT-PMP port mapping. It can be downloaded from here. NAT-PMP support is compiled in and turned off by default.
The legacy wallet uses Berkeley DB. To ensure backwards compatibility it is recommended to use Berkeley DB 4.8. If you have to build it yourself, and don't want to use any other libraries built in depends, you can do:
make -C depends NO_BOOST=1 NO_LIBEVENT=1 NO_QT=1 NO_SQLITE=1 NO_NATPMP=1 NO_UPNP=1 NO_ZMQ=1 NO_USDT=1
...
to: /path/to/qtum/depends/x86_64-pc-linux-gnuand configure using the following:
export BDB_PREFIX="/path/to/qtum/depends/x86_64-pc-linux-gnu"
./configure \
BDB_LIBS="-L${BDB_PREFIX}/lib -ldb_cxx-4.8" \
BDB_CFLAGS="-I${BDB_PREFIX}/include"Note: You only need Berkeley DB if the legacy wallet is enabled (see Disable-wallet mode).
To help make your Qtum Core installation more secure by making certain attacks impossible to exploit even if a vulnerability is found, binaries are hardened by default. This can be disabled with:
Hardening Flags:
./configure --enable-hardening
./configure --disable-hardening
Hardening enables the following features:
-
Position Independent Executable: Build position independent code to take advantage of Address Space Layout Randomization offered by some kernels. Attackers who can cause execution of code at an arbitrary memory location are thwarted if they don't know where anything useful is located. The stack and heap are randomly located by default, but this allows the code section to be randomly located as well.
On an AMD64 processor where a library was not compiled with -fPIC, this will cause an error such as: "relocation R_X86_64_32 against `......' can not be used when making a shared object;"
To test that you have built PIE executable, install scanelf, part of paxutils, and use:
scanelf -e ./qtumThe output should contain:
TYPE ET_DYN
-
Non-executable Stack: If the stack is executable then trivial stack-based buffer overflow exploits are possible if vulnerable buffers are found. By default, Qtum Core should be built with a non-executable stack, but if one of the libraries it uses asks for an executable stack or someone makes a mistake and uses a compiler extension which requires an executable stack, it will silently build an executable without the non-executable stack protection.
To verify that the stack is non-executable after compiling use:
scanelf -e ./qtumThe output should contain: STK/REL/PTL RW- R-- RW-
The STK RW- means that the stack is readable and writeable but not executable.
When the intention is to only run a P2P node, without a wallet, Qtum Core can be compiled in disable-wallet mode with:
./configure --disable-wallet
In this case there is no dependency on SQLite or Berkeley DB.
Mining is also possible in disable-wallet mode using the getblocktemplate RPC call.
A list of additional configure flags can be displayed with:
./configure --help
This example lists the steps necessary to setup and build a command line only distribution of the latest changes on Arch Linux:
pacman --sync --needed autoconf automake boost gcc git libevent libtool make pkgconf python sqlite gmp
git clone https://github.com/qtumproject/qtum --recursive
cd qtum/
./autogen.sh
./configure
make check
./src/qtumd
If you intend to work with legacy Berkeley DB wallets, see Berkeley DB section.