1. Home
  2. Knowledge Base
  3. Wallet Build Guide
  4. Linux Build Guide

Before you start

Always use absolute paths to configure and compile vulcano and the dependencies, for example, when specifying the path of the dependency:

../dist/configure –enable-cxx –disable-shared –with-pic –prefix=$BDB_PREFIX

Here BDB_PREFIX must absolute path – it is defined using $(pwd) which ensures the usage of the absolute path.

To Build

Copy and paste these lines in one at a time:

./autogen.sh
./configure
make
make install # optional

This will also build vulcano-qt if the dependencies are met.

Dependencies

These dependencies are required to build vulcano-qt:

 

Library Purpose Description
libssl SSL Support Secure communications
libboost Boost C++ Library

 

Optional dependencies:

 

Library Purpose Description
miniupnpc UPnP Support Firewall-jumping support
libdb4.8 Berkeley DB Wallet storage (only needed when the wallet is enabled)
qt GUI GUI toolkit (only needed when the GUI is enabled)
protobuf Payments in GUI Data interchange format used for payment protocol (only needed when the GUI is enabled)
libqrencode QR codes in GUI Optional for generating QR codes (only needed when the GUI is enabled)

For the versions used in the release, see release-process.md under Fetch and build inputs.

System requirements

C++ compilers can be very memory intensive, so it is recommended to have at least 1 GB of memory available when compiling the Vulcano Core. With 512MB of memory or less, compilation may take much longer due to swap thrashing.

Dependency Build Instructions

Build requirements:

sudo apt-get install build-essential libtool autotools-dev autoconf pkg-config libssl-dev

For Ubuntu 12.04 and later or Debian 7 and later libboost-all-dev will need to be installed:

sudo apt-get install libboost-all-dev

db4.8 packages are available here. You can add the repository using the following command:

sudo add-apt-repository ppa:bitcoin/bitcoin
sudo apt-get update

Ubuntu 12.04 and later have packages for libdb5.1-dev and libdb5.1++-dev, but using these will break binary wallet compatibility, and is not recommended.

For other Debian & Ubuntu (with ppa):

sudo apt-get install libdb4.8-dev libdb4.8++-dev

Optional:

sudo apt-get install libminiupnpc-dev (see –with-miniupnpc and –enable-upnp-default)

Dependencies for the GUI

If you want to build Vulcano-Qt, make sure that the required packages for Qt development are installed. Qt 5 is necessary to build the GUI. If both Qt 4 and Qt 5 are installed, Qt 5 will be used. To build without GUI pass –without-gui.

For Qt 5 you will need the following:

sudo apt-get install libqt5gui5 libqt5core5a libqt5dbus5 qttools5-dev qttools5-dev-tools libprotobuf-dev protobuf-compiler

libqrencode (optional) can be installed with:

sudo apt-get install libqrencode-dev

Once these are installed, they will be found by the configure command, and a vulcano-qt executable will be built by default.

Notes

The release is built with GCC and then “strip vulcanod” to strip the debug symbols, which reduces the executable size by about 90%.

miniupnpc

miniupnpc may be used for UPnP port mapping, which can be downloaded from here. UPnP support is compiled in and turned off by default. See the configure options for upnp behavior desired:

–without-miniupnpc      No UPnP support miniupnp not required
–disable-upnp-default   (the default) UPnP support is turned off by default at runtime
–enable-upnp-default    UPnP support is turned on by default at runtime

To build:

tar -xzvf miniupnpc-1.6.tar.gz
cd miniupnpc-1.6
make
sudo su
make install

Berkeley DB

It is recommended to use Berkeley DB 4.8. If you have to build it yourself, input the following commands:

Vulcano_ROOT=$(pwd)

# Pick a path to install BDB to, here we will create a directory within the Vulcano directory:

BDB_PREFIX=”${Vulcano_ROOT}/db4″
mkdir -p $BDB_PREFIX

# Fetch the source and verify that it is not tampered with:

wget ‘http://download.oracle.com/berkeley-db/db-4.8.30.NC.tar.gz’
echo ’12edc0df75bf9abd7f82f821795bcee50f42cb2e5f76a6a281b85732798364ef  db-4.8.30.NC.tar.gz’ | sha256sum -c
# -> db-4.8.30.NC.tar.gz: OK
tar -xzvf db-4.8.30.NC.tar.gz

# Build the library and install it to our prefix:

cd db-4.8.30.NC/build_unix/
#  Note: Do a static build so that it can be embedded into the executable, instead of having to find a .so at runtime:

../dist/configure –enable-cxx –disable-shared –with-pic –prefix=$BDB_PREFIX
make install

# Configure Vulcano Core to use our own-built instance of BDB:

cd $Vulcano_ROOT
./configure (other args…) LDFLAGS=”-L${BDB_PREFIX}/lib/” CPPFLAGS=”-I${BDB_PREFIX}/include/”

Note: You only need Berkeley DB if the wallet is enabled (see the section Disable-Wallet mode below).

Boost

If you need to build Boost yourself:

sudo su
./bootstrap.sh
./bjam install

Security

To help make your Vulcano installation more secure by making certain attacks impossible to exploit, even if a vulnerability is found, binaries are hardened by default. This can be disabled with:

Hardening Flags

./configure –enable-hardening
./configure –disable-hardening

Hardening enables the following features:

  • Position Independent Executable Build position independent code to take advantage of Address Space Layout Randomization offered by some kernels. An attacker who is able to cause execution of code at an arbitrary memory location is thwarted if the attacker doesn’t know where any useful information is located. The stack and heap are randomly located by default, and this also allows the code section to be randomly located as well.
  • On an Amd64 processor where a library was not compiled with -fPIC, this will cause an error such as: “relocation R_X86_64_32 against `……’ can not be used when making a shared object;”
  • To test that you have built PIE executable, install scanelf, part of paxutils, and use: scanelf -e ./vulcano
  • The output should contain: TYPE ET_DYN
  • Non-executable Stack: If the stack is executable, then trivial stack based buffer overflow exploits are possible if vulnerable buffers are found. By default, Vulcano should be built with a non-executable stack, but if one of the libraries it uses asks for an executable stack or someone makes a mistake and uses a compiler extension which requires an executable stack, it will silently build an executable without the non-executable stack protection.
  • To verify that the stack is non-executable after compiling, use: scanelf -e ./vulcanod
  • The output should contain: STK/REL/PTL RW- R– RW-
  • The STK RW- means that the stack is readable and writable, but not executable.

 

Related Articles