Comment 2 for bug 1172711

In order for the compilation to succeed, a few prerequisites exist. On my 64-bit Ubuntu 12.04 virtual system (3.2.0-40-virtual), the packages I needed were:

automake, libtool, openjdk-7-jdk

A later attachment is the deb package (prepared by checkconfig) on which the attached tarball is dependent. Once that deb is installed, deploy the attached tarball, and then do, in its directory:

./bootstrap &> bootstrap.log
./configure --with-java-jdk=/usr/lib/jvm/jdk --with-jni-interface &> configure.log
make &> make.log
sudo checkinstall make install

Where /usr/lib/jvm/jdk is the path of your JDK (e.g. /usr/lib/jvm/java-7-openjdk-amd64)

You should get a log similar to this when the install fails (I named the package lttng-ust-java):

Selecting previously unselected package lttng-ust-java.
(Reading database ... 147274 files and directories currently installed.)
Unpacking lttng-ust-java (from .../lttng-ust-java_2.2.0-rc1-12_amd64.deb) ...
dpkg: error processing /home/daniel/Documents/git.lttng.org/lttng-ust-2.2.0-rc1+-a16877a-Java/lttng-ust-java_2.2.0-rc1-12_amd64.deb (--install):
 unable to create `/proc/self/coredump_filter.dpkg-new' (while processing `./proc/self/coredump_filter'): No such file or directory
Processing triggers for man-db ...
Errors were encountered while processing:
 /home/daniel/Documents/git.lttng.org/lttng-ust-2.2.0-rc1+-a16877a-Java/lttng-ust-java_2.2.0-rc1-12_amd64.deb

I know, it's weird, but this bug may be somehow related to the Java business, because the tarball packages fine when the Java support is omitted.

This is nothing dramatic, mind you, as I only needed to deploy the deb, remove the offending proc sub-directory, and repackage it to get a working version.