CRIU uses the C bindings of Google's Protocol Buffers. The easiest approach for most would be to install a distribution packages. RPM package namenames: <code>protobuf-compiler</code>,<code>protobuf-c-devel</code>. Debian package namenames: <code>protobuf-compiler</code>, <code>libprotobuf-c0-dev</code>.

If you would like to build from source instead of using a package, the Protocol Buffer library can be found at http://code.google.com/p/protobuf/, while the Protocol Buffer C bindings can be found at http://code.google.com/p/protobuf-c/. You you can use the following commands to obtain the source code repositories via <code>git</code>. Note that when cross compiling you will need to compile once for your build machine in order to get a <code>protoc</code> binary to use in the build process, configure, and build once for each target machine to generate <code>libprotobuf-c.so</the code>.

./configure --prefix=`pwd`/../`uname -m`

cd .. If you are cross compiling, then you will additionally want to build a version for your target architecture. This example targets AArch64.  cd protobuf ./configure --host=aarch64-linux-gnu --prefix=`pwd`/aarch64 --with-protoc=`pwd`/`uname -m`/bin/protoc make make install cd ..

./autogen.sh ./configure --prefix=`pwd`/`uname -m` PATH="`pwd`/../protobuf/`uname -m`/bin:$PATH"--disable-protoc