3. Run the autobuild.sh command and install all the dev libraries it tells you are missing.
./autobuild.sh
I needed to install at least build-essential, libtool, python-gtk2-dev, and libsasl2-dev (ie Synaptic or with the sudo apt-get install command).
I got the error "libtool: link: only absolute run-paths are allowed" at the end of the build, but the new library had been built successfully as build/src/.libs/libgtk-vnc-1.0.so.0.0.1 and I just needed to link it to /usr/lib/libgtk-vnc-1.0.so to get it working.
The upstream bug (https:/ /bugzilla. gnome.org/ show_bug. cgi?id= 577580) has a patch for libgtk-vnc that fixes the bug.
For those interested, you can apply it with:
1. Make a folder for the gtk-vnc git source code and download it:
mkdir gtk-vnc gnome.org/ gtk-vnc
cd gtk-vnc
git clone git://git.
2. Apply the patch (http:// bugzilla- attachments. gnome.org/ attachment. cgi?id= 148702)
wget http:// bugzilla- attachments. gnome.org/ attachment. cgi?id= 148702 -o pointer-patch.diff
patch -p1 < pointerpatch.diff
3. Run the autobuild.sh command and install all the dev libraries it tells you are missing.
./autobuild.sh
I needed to install at least build-essential, libtool, python-gtk2-dev, and libsasl2-dev (ie Synaptic or with the sudo apt-get install command).
I got the error "libtool: link: only absolute run-paths are allowed" at the end of the build, but the new library had been built successfully as build/src/ .libs/libgtk- vnc-1.0. so.0.0. 1 and I just needed to link it to /usr/lib/ libgtk- vnc-1.0. so to get it working.