>
> Isn't nproc or nproc+1 too much? On systems with hyper-threading,
> this will try using too many jobs, and might cause the system be
> significantly less responsive. Maybe nproc/2 is a better default?
>
This is an interesting question and I suppose the answer depends on many
factors. At my o
> ... remove all those .EXPORT_ALL_VARIABLES: settings. This is just a
very bad idea.
Sorry for the side-track but in my experience exporting *any* make variable
is a bad idea. Where I work we maintain a "Make Bible" which says something
to the effect that the only time it makes sense to export
Minor suggestion: In 9.7 Temporary Files the manual says "These files must
not be disturbed while make is running" but it doesn't say what "these
files" look like. Assuming the names have some pattern, would it make sense
to be more specific and say something like "do not remove temp files
matching
I think this little nit should be cleared up. In one place the manual says:
... after parsing GNUMAKEFLAGS GNU make sets this variable to the empty
string ...
But in another place it says:
GNU make never sets this variable itself.
The meaning is clear (to me) but the language is not well formed
