This section is only relevant when you are installing from source. We will assume that you have obtained a source tarball from, e.g. divine-@version@.tar.gz.
We regularly build divine on Linux and OpenBSD, though other POSIX-compatible systems (including macOS) should also work. There is currently no support for running divine on Windows natively (but it should work under WSL). If you do not want to build divine from sources, you can download a static binary.


To build divine, you will need the following:
  • a C++17 compiler (gcc or clang),
  • make,
  • perl,
  • zlib,
  • libedit (along with ncurses).
If you use Debian, Ubuntu, Fedora or Arch Linux, or a derivative thereof, you can run make install-deps in the directory with the sources (or sh releng/ if you don't have make yet).
$ tar xvzf divine-@version@.tar.gz
$ cd divine-@version@
$ make install-deps
Please note that a release build needs about 12GB of disk space and 8GB of RAM.


First, unzip the distribution tarball and enter the newly created directory
$ tar xvzf divine-@version@.tar.gz
$ cd divine-@version@
In most cases, the build should be fully automatic. However, if you need to change the path to a compiler, compiler flags, or make other similar adjustments, look at the top of the file gib/main. You can either directly edit that file, or you can copy the relevant lines into gib/local and edit the variables there.
To build divine, run:
$ make
After a while, you should obtain the main divine binary. You can check that this is indeed the case by running:
$ ./_build.default/tools/divine help