We were saying "-jN means using N cores (or N threads)". This is
completely wrong. "-jN" only tells the building system to run N jobs
simultaneously, but each job can start their own subprocesses or threads
and there is no way for the building system to know how many
subprocesses or threads a job will start.
This caused a lot of misunderstandings and encouraged users to wrongly
blame building systems.
Fix the description of -jN, and add how to use cgroup to control the
usage of CPU cores and system RAM.
On a systemd-based system, systemd is the cgroup manager and manually
operating on cgroups may puzzle systemd. So use systemd-run for
creating and setting up cgroup. On a sysv-based system create and set
up the cgroup manually.
- Do not use the single quote "'" for *everything*. Use a proper XML
tag if applicable.
- Don't call the source directory "build" directory because we now often
create a subdirectory named "build", so calling the source directory
"build" can be puzzling.
- Update the method to use compressed patch (matching libpng
instruction).
- Explain why ninja attempts to use N+1 or N+2 logical processors.
- Now we don't run test suites w/o parallel jobs.
- Use "less" instead of "more" as "less" is actually more powerful.
- Explain -mtune=.
- -DNDEBUG is not always implied by --buildtype=release, but it's
sometimes implied.
- Alert that some "Skylake"s are actually not -march=skylake.
- For Rust, explain "-O" and "-g".
- libtool is usually internally shipped and system libtool is not used.
Or we can simply patch system libtool to stop installing .la files...
- Add a paragraph about static library. Prevent anyone from thinking
"oh I need static libraries and I'll keep those .la files".
- Mention that .la file may mistakenly include library names or paths
not valid after installation.
- Move a </literal> into the correct location.
Two entities downloads-root-systemd and patch-root were not
modified when switching to release:
- change the name of downloads-root-systemd to downloads-root since
the aim is to not have "-systemd" entities, and use "&blfs-version;"
for it
- create a patch-version entity (this one does not change for
systemd), and use it in patch-root
Update to tree-2.0.0.
Update to pango-1.50.3.
Update to qpdf-10.5.0.
Update to libportal-0.5.
Update to gtk+3 3.24.31.
Update URLs in Beyond BLFS section.
I know it is somewhat useless, but I don't like them for
two reasons: first they cannot be seen, and I do not like things I
cannot see. Second, git highlights them, and this is disturbing...
