> I'm not sure what "documentation, not manual" refers to.
Maybe you mean the man page? Yes. ~~~ $ man man General
Commands Manual man - format and display the on-line manual pages ~~~
According to this man pages are manuals. > It's not expected that
users lo
See the last 5 paragraphs, starting with: The MAKEFLAGS variable can also be
useful if you want to have certain options, such as ‘-k’ (see Summary of
Options), set each time you run make.Tried to get what the `MAKEFLAGS'
is but documentation, not manual is not very helpful. Info is bette
The other is that it's difficult to set a generic value for "-j"
(say in a MAKEFLAGS environment variable, or even in the makefile itself)
that works across a variety of systems with different CPU counts. What is
MAKEFLAGS? As far as I understand it is command line in form of environmental
> The other is that it's difficult to set a generic value for
"-j" (say > in a MAKEFLAGS environment variable, or even in the
makefile itself) > that works across a variety of systems with different
CPU counts. What is MAKEFLAGS? As far as I understand it is command line in
form of environm
I don't see any need to be aggressive in your response. You're right,
it came out clumsily. I can get -j almost 2x the number of CPU threads
before builds start slowing down, Maybe that 2*nproc is not that bad
estimate, if it comes out I experiments. (b) there's a lot of latency of
> Emotive terminology like "ludicrous" doesn't encourage a
constructive response. You're right. I don't feel in English so it
may be too strong or even not to the point. >> Here is [a] slightly
improved test script[.]>... yet I didn't see one. Script is here:
lists.gnu.org https://li
Mentioned script.
#!/bin/sh
#URL=http://ftp.gnu.org/gnu/make/make-4.4.1.tar.gz # 34 .o files
#URL=https://mirrors.dotsrc.org/gnu/make/make-4.4.1.tar.gz
URL=https://mirrors.dotsrc.org/gnu/bash/bash-5.2.tar.gz # 193
#URL=https://mirrors.dotsrc.org/gnu/coreutils/coreutils-9.5.tar.gz # ~1859 .c
#URL=h
> There are plenty of scenarios where using more jobs than processor threads
results in faster builds: it all depends You say that because you have tested
it or because you believe it? I have tested it, But let's bust this
ludicrous idea and show us a test that disproves me. Here is slightly
Autodetect processing units with -jAt the moment, though this moment lasts
for decades now, -j/--jobs without argument starts infinite number of parallel
jobs. Practice shows that compilation with jobs bigger than number of
available threads is not faster in any way, only uses more memory a
