Compilation instructions

Contents 1 Compiling Zabbix 1.1 From source archives 1.2 From SVN checkout 1.2.1 Prerequisites 1.2.2 Generating configure script 1.2.3 Creating source archive

Compiling Zabbix

From source archives

For compilation from source archives (released versions or nightly builds), please see official 1.8 installation instructions or 2.0 installation instructions.

From SVN checkout

Compiling Zabbix from SVN checkout is slightly different and more complex than doing the same from a released package.

Prerequisites

Make sure you have got pkg-config installed prior running bootstrap.sh, or you will receive an error like this:

   ./configure: line 8092: syntax error near unexpected token `IKSEMEL,iksemel,'

Generating configure script

To generate configure, run :

 ./bootstrap.sh

At this point, you can run configure and compile Zabbix directly in the checkout directory. Read below for a suggested approach instead.

Creating source archive

It is suggested to create source archive, just like the one that can be downloaded from the official pages. If you like a clean checkout, copy it first to some other directory for package creation purposes. To do this more than once, rsync will be helpful, as less files will have to be copied in the consequent runs:

 mkdir /tmp/zabbix
 rsync -r --exclude='*/.svn*' trunk /tmp/zabbix

Unfortunately, to do this, configure script has to be run, thus the machine will need at least the basic dependencies, needed for actual Zabbix compilation. To reduce amount of libraries needed, run configure without any parameters:

 ./configure

This should complete without errors. If it doesn't, resolve missing dependencies. Next we have to generate database schema files:

 make dbschema

And then comes actual distribution package step:

 make dist

This should leave you with zabbix-<version>.tar.gz file in the /tmp/zabbix/trunk directory, for example, /tmp/zabbix/trunk/zabbix-1.9.7.tar.gz.

For Zabbix trunk (1.9 versions since revision 15656), it is necessary to generate translation files if you wish to use other languages but English. To do that, run:

 make gettext

Utility msgfmt from gettext package is required to generate mo files.