diff options
| author | jonatack <jon@atack.com> | 2021-07-23 20:59:54 +0530 |
|---|---|---|
| committer | fanquake <fanquake@gmail.com> | 2021-07-29 11:05:48 +0800 |
| commit | 8f1e3b31b2b4ba024b2adca31a061bbbd2a1378f (patch) | |
| tree | c2b8adc892f7d079c90a6434e2e1e96d90c09c59 | |
| parent | 3bbfc1b8e0660a03c7b63eaf2fc8834b499aa811 (diff) | |
script, doc: guix touchups
Github-Pull: #22538
Rebased-From: 198ceb82f91bfdeac6e143ca7433f4a524f6f36f
| -rw-r--r-- | contrib/guix/README.md | 7 | ||||
| -rw-r--r-- | doc/build-openbsd.md | 2 |
2 files changed, 4 insertions, 5 deletions
diff --git a/contrib/guix/README.md b/contrib/guix/README.md index fa7f63af87..2bb464a40d 100644 --- a/contrib/guix/README.md +++ b/contrib/guix/README.md @@ -11,7 +11,7 @@ We achieve bootstrappability by using Guix as a functional package manager. # 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 - 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 start over. -1. Uninstall Guix itself according to the way you installed it. (e.g. `sudo apt - purge guix` for Ubuntu packaging, `sudo make uninstall` for - built-from-source). +1. Uninstall Guix itself according to the way you installed it (e.g. `sudo apt + purge guix` for Ubuntu packaging, `sudo make uninstall` for a build from source). 2. Remove all build users and groups You may check for relevant users and groups using: diff --git a/doc/build-openbsd.md b/doc/build-openbsd.md index 89fd506f13..6e54f67edc 100644 --- a/doc/build-openbsd.md +++ b/doc/build-openbsd.md @@ -68,7 +68,7 @@ export AUTOMAKE_VERSION=1.16 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, -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. (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 |