mirror of
https://github.com/dashpay/dash.git
synced 2024-12-25 20:12:57 +01:00
649eaa44a1
01cd24c22606408d5c0ac74c9a2c5d85eff77846 doc: set CC_FOR_BUILD when building on OpenBSD (fanquake) Pull request description: Closes: #19559 While #19559 has been fixed upstream, it makes sense to not only recommend using `CC_FOR_BUILD`here until the fix is pulled in as part of our next libsecp update, but after discussing with Cory, he suggested we should be setting this on OpenBSD (which still has the an ancient GCC) regardless. ACKs for top commit: real-or-random: ACK 01cd24c22606408d5c0ac74c9a2c5d85eff77846 I looked at the diff (but can't test the instructions on OpenBSD) laanwj: Code review ACK 01cd24c22606408d5c0ac74c9a2c5d85eff77846 Tree-SHA512: 322802b9303771f1be2ad9628f268dfa71dc7ee77948fa2a34f21eceb19b2d8efdd8876c8f0778adbfcde48fa0f88cd4e698ae425428159abca38e8c7980da1d
111 lines
3.2 KiB
Markdown
111 lines
3.2 KiB
Markdown
OpenBSD build guide
|
|
======================
|
|
(updated for OpenBSD 6.7)
|
|
|
|
This guide describes how to build dashd, dash-qt, and command-line utilities on OpenBSD.
|
|
|
|
Preparation
|
|
-------------
|
|
|
|
Run the following as root to install the base dependencies for building:
|
|
|
|
```bash
|
|
pkg_add git gmake libevent libtool
|
|
pkg_add qt5 # (optional for enabling the GUI)
|
|
pkg_add autoconf # (select highest version, e.g. 2.69)
|
|
pkg_add automake # (select highest version, e.g. 1.15)
|
|
pkg_add python # (select highest version, e.g. 3.8)
|
|
pkg_add gmp
|
|
pkg_add boost
|
|
|
|
git clone https://github.com/dashpay/dash.git
|
|
```
|
|
|
|
See [dependencies.md](dependencies.md) for a complete overview.
|
|
|
|
**Important**: From OpenBSD 6.2 onwards a C++11-supporting clang compiler is
|
|
part of the base image, and while building it is necessary to make sure that
|
|
this compiler is used and not ancient g++ 4.2.1. This is done by appending
|
|
`CC=cc CC_FOR_BUILD=cc CXX=c++` to configuration commands. Mixing different
|
|
compilers within the same executable will result in errors.
|
|
|
|
### Building BerkeleyDB
|
|
|
|
BerkeleyDB is only necessary for the wallet functionality. To skip this, pass
|
|
`--disable-wallet` to `./configure` and skip to the next section.
|
|
|
|
It is recommended to use Berkeley DB 4.8. You cannot use the BerkeleyDB library
|
|
from ports, for the same reason as boost above (g++/libstd++ incompatibility).
|
|
If you have to build it yourself, you can use [the installation script included
|
|
in contrib/](/contrib/install_db4.sh) like so:
|
|
|
|
```bash
|
|
./contrib/install_db4.sh `pwd` CC=cc CXX=c++
|
|
```
|
|
|
|
from the root of the repository. Then set `BDB_PREFIX` for the next section:
|
|
|
|
```bash
|
|
export BDB_PREFIX="$PWD/db4"
|
|
```
|
|
|
|
### Building Dash Core
|
|
|
|
**Important**: Use `gmake` (the non-GNU `make` will exit with an error).
|
|
|
|
Preparation:
|
|
```bash
|
|
export AUTOCONF_VERSION=2.69 # replace this with the autoconf version that you installed
|
|
export AUTOMAKE_VERSION=1.15 # replace this with the automake version that you installed
|
|
./autogen.sh
|
|
```
|
|
Make sure `BDB_PREFIX` is set to the appropriate path from the above steps.
|
|
|
|
To configure with wallet:
|
|
```bash
|
|
./configure --with-gui=no CC=cc CXX=c++ \
|
|
BDB_LIBS="-L${BDB_PREFIX}/lib -ldb_cxx-4.8" \
|
|
BDB_CFLAGS="-I${BDB_PREFIX}/include" \
|
|
MAKE=gmake
|
|
```
|
|
|
|
To configure without wallet:
|
|
```bash
|
|
./configure --disable-wallet --with-gui=no CC=cc CC_FOR_BUILD=cc CXX=c++ MAKE=gmake
|
|
```
|
|
|
|
To configure with GUI:
|
|
```bash
|
|
./configure --with-gui=yes CC=cc CXX=c++ \
|
|
BDB_LIBS="-L${BDB_PREFIX}/lib -ldb_cxx-4.8" \
|
|
BDB_CFLAGS="-I${BDB_PREFIX}/include" \
|
|
MAKE=gmake
|
|
```
|
|
|
|
Build and run the tests:
|
|
```bash
|
|
gmake # use -jX here for parallelism
|
|
gmake check
|
|
```
|
|
|
|
Resource limits
|
|
-------------------
|
|
|
|
If the build runs into out-of-memory errors, the instructions in this section
|
|
might help.
|
|
|
|
The standard ulimit restrictions in OpenBSD are very strict:
|
|
|
|
data(kbytes) 1572864
|
|
|
|
This, unfortunately, in some cases not enough to compile some `.cpp` files in the project,
|
|
(see issue [#6658](https://github.com/bitcoin/bitcoin/issues/6658)).
|
|
If your user is in the `staff` group the limit can be raised with:
|
|
|
|
ulimit -d 3000000
|
|
|
|
The change will only affect the current shell and processes spawned by it. To
|
|
make the change system-wide, change `datasize-cur` and `datasize-max` in
|
|
`/etc/login.conf`, and reboot.
|
|
|