Steffen Nurpmeso wrote in
<20221105222339.z0b2x%stef...@sdaoden.eu>:
...
| #?0|kent:s-nail-14.9.24$ ../make-4.4/make all -j4
| ...
|All good
| ...
| #?0|kent:s-nail-14.9.24$ make distclean
| make[1]: Entering directory '/tmp/x/s-nail-14.9.24/.obj'
| make[1]: *** Cannot open jobserver /tmp/GMfifo31074: No such file \
| or directory. Stop.
| make[1]: Leaving directory '/tmp/x/s-nail-14.9.24/.obj'
| make: *** [makefile:40: distclean] Error 2
|
|It seems GNU make now embeds volatile information into $MAKEFLAGS,
|but refrains from working if that is invalid.
This hinders build systems which aim in being portable and easy,
in that users simply call "make" and that calls some shell script
for configuration by itself (instead of the typical GNU style
"./configure && make && make install).
I do, for example, and in the shell script i do
COMMLINE="${*}"
in order to pick up things the user gave on the command line.
(The software can be configured via command line arguments, say
$ make OPT_POP3=no OPT_SMTP=require tangerine)
...
|I wonder, or, to be honest, it is my opinion that GNU make should
|reset this part of MAKEFLAGS in at least the ENOENT case?
...
--steffen
|
|Der Kragenbaer, The moon bear,
|der holt sich munter he cheerfully and one by one
|einen nach dem anderen runter wa.ks himself off
|(By Robert Gernhardt)
