READMEs updates

Author: ilg-ul

README-BUILD.md

@@ -143,8 +143,8 @@ file.
 
 ### Build
 
-The builds currently run on 3 dedicated machines (Intel GNU/Linux,
-Arm GNU/Linux and Intel macOS). A fourth machine for Arm macOS is planned.
+The builds currently run on 5 dedicated machines (Intel GNU/Linux,
+Arm 32 GNU/Linux, Arm 64 GNU/Linux, Intel macOS and Arm macOS.
 
 #### Build the Intel GNU/Linux and Windows binaries
 
@@ -201,7 +201,7 @@ network connection or a computer entering sleep.
 screen -S qemu
 
 sudo rm -rf ~/Work/qemu-riscv-*-*
-bash ${HOME}/Work/qemu-riscv-xpack.git/scripts/helper/build.sh --develop --all
+bash ${HOME}/Work/qemu-riscv-xpack.git/scripts/helper/build.sh --develop --linux64 --win64
 ```
 
 or, for development builds:
@@ -260,8 +260,9 @@ The result should look similar to:
 ```console
 $ docker images
 REPOSITORY       TAG                      IMAGE ID       CREATED          SIZE
-ilegeul/ubuntu   arm32v7-16.04-xbb-v3.3   a0ceaa6dad05   57 minutes ago   3.34GB
-ilegeul/ubuntu   arm64v8-16.04-xbb-v3.3   1b0b4a94de6d   13 hours ago     3.6GB
+hello-world      latest                   46331d942d63   6 weeks ago     9.14kB
+ilegeul/ubuntu   arm64v8-18.04-xbb-v3.4   4e7f14f6c886   4 months ago    3.29GB
+ilegeul/ubuntu   arm32v7-18.04-xbb-v3.4   a3718a8e6d0f   4 months ago    2.92GB
 ```
 
 Since the build takes a while, use `screen` to isolate the build session
@@ -272,14 +273,14 @@ network connection or a computer entering sleep.
 screen -S qemu
 
 sudo rm -rf ~/Work/qemu-riscv-*-*
-bash ${HOME}/Work/qemu-riscv-xpack.git/scripts/helper/build.sh --develop --all
+bash ${HOME}/Work/qemu-riscv-xpack.git/scripts/helper/build.sh --develop --arm64 --arm32
 ```
 
 or, for development builds:
 
 ```sh
 sudo rm -rf ~/Work/qemu-riscv-*-*
-bash ${HOME}/Work/qemu-riscv-xpack.git/scripts/helper/build.sh --develop --without-pdf --without-html --disable-tests --arm32 --arm64
+bash ${HOME}/Work/qemu-riscv-xpack.git/scripts/helper/build.sh --develop --without-html --disable-tests --arm64 --arm32
 ```
 
 To detach from the session, use `Ctrl-a` `Ctrl-d`; to reattach use
@@ -308,7 +309,6 @@ The current platforms for macOS production builds are:
 
 ```sh
 caffeinate ssh xbbmi
-
 caffeinate ssh xbbma
 ```
 
@@ -327,7 +327,7 @@ or, for development builds:
 
 ```sh
 rm -rf ~/Work/qemu-riscv-*-*
-caffeinate bash ${HOME}/Work/qemu-riscv-xpack.git/scripts/helper/build.sh --develop --without-pdf --without-html --disable-tests --macos
+caffeinate bash ${HOME}/Work/qemu-riscv-xpack.git/scripts/helper/build.sh --develop --without-html --disable-tests --macos
 ```
 
 To detach from the session, use `Ctrl-a` `Ctrl-d`; to reattach use
@@ -357,7 +357,7 @@ Instead of `--all`, you can use any combination of:
 On Arm, instead of `--all`, you can use any combination of:
 
 ```console
---arm32 --arm64
+--arm64 --arm32
 ```
 
 #### clean

README-RELEASE.md

@@ -84,7 +84,7 @@ With a git client, go to the helper repo and update to the latest master commit.
 
 ### Development run the build scripts
 
-Before the real build, run a test build on the development machine (`wks`)
+Before the real build, run a test build on the development machine (`wksi`)
 or the production machines (`xbbma`, `xbbmi`):
 
 ```sh
@@ -131,12 +131,12 @@ The automation is provided by GitHub Actions and three self-hosted runners.
 Run the `generate-workflows` to re-generate the
 GitHub workflow files; commit and push if necessary.
 
-- on the macOS machine (`xbbmi`) open ssh sessions to the Linux
-machines (`xbbli`, `xbbla64` and `xbbla32`):
+- on the macOS machine (`xbbmi`) open ssh sessions to the build
+machines (`xbbma`, `xbbli`, `xbbla64` and `xbbla32`):
 
 ```sh
+caffeinate ssh xbbma
 caffeinate ssh xbbli
-
 caffeinate ssh xbbla64
 caffeinate ssh xbbla32
 ```
@@ -312,7 +312,7 @@ watching this project.
   possibly adjust `.npmignore`
 - `npm version 6.2.0-1.1`; the first 5 numbers are the same as the
   GitHub release; the sixth number is the npm specific version
-- the commits and the tag should have beed pushed by the `postversion` script;
+- the commits and the tag should have been pushed by the `postversion` script;
   if not, push them with `git push origin --tags`
 - `npm publish --tag next` (use `--access public` when publishing for
   the first time)