foster/bitcoin-core
0
0
Fork 0
mirror of https://github.com/bitcoin/bitcoin.git synced 2025-03-11 15:56:58 -04:00
Code Issues Activity

script, doc: guix touchups

Browse source
This commit is contained in:
jonatack 2021-07-23 20:59:54 +05:30 • committed by h
parent d7b7f610a5
commit 198ceb82f9
2 changed files with 4 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
contrib/guix/README.md
View file

@ -11,7 +11,7 @@ We achieve bootstrappability by using Guix as a functional package manager.
# Requirements # Requirements
Conservatively, a x86_64 machine with: Conservatively, you will need an x86_64 machine with:
- 16GB of free disk space on the partition that /gnu/store will reside in - 16GB of free disk space on the partition that /gnu/store will reside in
- 8GB of free disk space **per platform triple** you're planning on building - 8GB of free disk space **per platform triple** you're planning on building
@ -437,9 +437,8 @@ In the extraordinarily rare case where you messed up your Guix installation in
an irreversible way, you may want to completely purge Guix from your system and an irreversible way, you may want to completely purge Guix from your system and
start over. start over.
1. Uninstall Guix itself according to the way you installed it. (e.g. `sudo apt 1. Uninstall Guix itself according to the way you installed it (e.g. `sudo apt
purge guix` for Ubuntu packaging, `sudo make uninstall` for purge guix` for Ubuntu packaging, `sudo make uninstall` for a build from source).
built-from-source).
2. Remove all build users and groups 2. Remove all build users and groups
You may check for relevant users and groups using: You may check for relevant users and groups using:

2
doc/build-openbsd.md
View file

@ -68,7 +68,7 @@ export AUTOMAKE_VERSION=1.16
Make sure `BDB_PREFIX` is set to the appropriate path from the above steps. Make sure `BDB_PREFIX` is set to the appropriate path from the above steps.
Note that building with external signer support currently fails on OpenBSD, Note that building with external signer support currently fails on OpenBSD,
hence you have to explicitely disable it by passing the parameter hence you have to explicitly disable it by passing the parameter
`--disable-external-signer` to the configure script. `--disable-external-signer` to the configure script.
(Background: the feature requires the header-only library boost::process, which (Background: the feature requires the header-only library boost::process, which
is available on OpenBSD 6.9 via Boost 1.72.0, but contains certain system calls is available on OpenBSD 6.9 via Boost 1.72.0, but contains certain system calls