1 Copyright (c) 2009-2010 Satoshi Nakamoto
2 Copyright (c) 2011 Bitcoin Developers
3 Distributed under the MIT/X11 software license, see the accompanying
4 file license.txt or http://www.opensource.org/licenses/mit-license.php.
5 This product includes software developed by the OpenSSL Project for use in
6 the OpenSSL Toolkit (http://www.openssl.org/). This product includes
7 cryptographic software written by Eric Young (eay@cryptsoft.com) and UPnP
8 software written by Thomas Bernard.
18 make -f makefile.unix # Headless bitcoin
20 See readme-qt.rst for instructions on building Bitcoin QT,
21 the graphical bitcoin.
26 Library Purpose Description
27 ------- ------- -----------
28 libssl SSL Support Secure communications
29 libdb4.8 Berkeley DB Blockchain & wallet storage
30 libboost Boost C++ Library
31 miniupnpc UPnP Support Optional firewall-jumping support
32 libqrencode QRCode generation Optional QRCode generation
34 miniupnpc may be used for UPnP port mapping. It can be downloaded from
35 http://miniupnp.tuxfamily.org/files/. UPnP support is compiled in and
36 turned off by default. Set USE_UPNP to a different value to control this:
37 USE_UPNP= No UPnP support - miniupnp not required
38 USE_UPNP=0 (the default) UPnP support turned off by default at runtime
39 USE_UPNP=1 UPnP support turned on by default at runtime
41 libqrencode may be used for QRCode image generation. It can be downloaded
42 from http://fukuchi.org/works/qrencode/index.html.en, or installed via
43 your package manager. Set USE_QRCODE to control this:
44 USE_QRCODE=0 (the default) No QRCode support - libarcode not required
45 USE_QRCODE=1 QRCode support enabled
47 Licenses of statically linked libraries:
48 Berkeley DB New BSD license with additional requirement that linked
49 software must be free open source
50 Boost MIT-like license
51 miniupnpc New (3-clause) BSD license
53 Versions used in this release:
60 Dependency Build Instructions: Ubuntu & Debian
61 ----------------------------------------------
62 sudo apt-get install build-essential
63 sudo apt-get install libssl-dev
64 sudo apt-get install libdb4.8-dev
65 sudo apt-get install libdb4.8++-dev
66 Boost 1.40+: sudo apt-get install libboost-all-dev
67 or Boost 1.37: sudo apt-get install libboost1.37-dev
68 sudo apt-get install libqrencode-dev
70 If using Boost 1.37, append -mt to the boost libraries in the makefile.
73 Dependency Build Instructions: Gentoo
74 -------------------------------------
76 Note: If you just want to install bitcoind on Gentoo, you can add the Bitcoin
77 overlay and use your package manager:
78 layman -a bitcoin && emerge bitcoind
80 emerge -av1 --noreplace boost glib openssl sys-libs/db:4.8
82 Take the following steps to build (no UPnP support):
84 make -f makefile.unix USE_UPNP= BDB_INCLUDE_PATH='/usr/include/db4.8'
90 The release is built with GCC and then "strip bitcoind" to strip the debug
91 symbols, which reduces the executable size by about 90%.
96 tar -xzvf miniupnpc-1.6.tar.gz
105 You need Berkeley DB 4.8. If you have to build Berkeley DB yourself:
106 ../dist/configure --enable-cxx
112 If you need to build Boost yourself:
120 To help make your bitcoin installation more secure by making certain attacks impossible to
121 exploit even if a vulnerability is found, you can take the following measures:
123 * Position Independent Executable
124 Build position independent code to take advantage of Address Space Layout Randomization
125 offered by some kernels. An attacker who is able to cause execution of code at an arbitrary
126 memory location is thwarted if he doesn't know where anything useful is located.
127 The stack and heap are randomly located by default but this allows the code section to be
128 randomly located as well.
130 On an Amd64 processor where a library was not compiled with -fPIC, this will cause an error
131 such as: "relocation R_X86_64_32 against `......' can not be used when making a shared object;"
133 To build with PIE, use:
134 make -f makefile.unix ... -e PIE=1
136 To test that you have built PIE executable, install scanelf, part of paxutils, and use:
139 The output should contain:
143 * Non-executable Stack
144 If the stack is executable then trivial stack based buffer overflow exploits are possible if
145 vulnerable buffers are found. By default, bitcoin should be built with a non-executable stack
146 but if one of the libraries it uses asks for an executable stack or someone makes a mistake
147 and uses a compiler extension which requires an executable stack, it will silently build an
148 executable without the non-executable stack protection.
150 To verify that the stack is non-executable after compiling use:
153 the output should contain:
157 The STK RW- means that the stack is readable and writeable but not executable.