" variant, in order to
avoid overloading or underloading the system without having to implement their
own heuristics. That way, a top-level script will be much more likely to
succeed at setting a global limit when launching third-party sub-makes in
parallel.
P
do the trick. I just want to spare the user the
effort to retrieve the CPU count, which is always a small,
system-dependant pain.
Please copy me on the answers, as I'm not on this list.
Regards,
R. Diez
___
Bug-make mailing list
Bug-make@gnu.org
o ""
echo ""
Is this an oversight? The manual does not mention any exceptions for
--warn-undefined-variables, and I wish that $(value ...) warned too.
Please copy me on the answers, as I'm not subscribed to this list.
Thanks,
R. Diez
___
Follow-up Comment #7, bug #57242 (project make):
About this statement below:
"This is necessary, because a command can mess up job server operation or a
command may expect a specific fd to be available."
a) I wonder how a command can mess up job server operation:
a1) One way would be that a pro
Follow-up Comment #8, bug #63439 (project make):
I don't thing this bug is fixed yet.
I am using the following makefile:
https://github.com/rdiez/DebugDue/tree/master/Toolchain
This is the command I am running:
$ make --no-builtin-variables --warn-undefined-variables help >/dev/null
make: warn
Follow-up Comment #10, bug #63439 (project make):
> Please be sure to post the output of *make --version*
> so we know what version of GNU Make you are using.
Sorry I forgot. I am using GNU Make 4.4.1, which I built from sources myself:
GNU Make 4.4.1
Built for x86_64-pc-linux-gnu
> Also plea
Follow-up Comment #13, bug #63439 (project make):
Thanks for confirming the issue I am reporting.
Could you please update the "Fixed Release: 4.4.1", as it is not actually
true?
Or if it is a separate issue to the one fixed in 4.4.1, then it would probably
be worth creating a new bug report for
