[bug #63867] Port to older versions of gnu tar.

2023-03-05 Thread Paul D. Smith
Follow-up Comment #2, bug #63867 (project make): I think the recent email is because the tar options are also used to generate the release tarball, not just to generate the tarball containing error results. Note that we manage these options simply by exporting the TAR_OPTIONS variable, which mean

[bug #63867] Port to older versions of gnu tar.

2023-03-05 Thread Paul D. Smith
Follow-up Comment #3, bug #63867 (project make): Of course when I say "every invocation of tar by GNU make" I obviously mean, in the GNU make source directory only. ___ Reply to this item at:

Re: 4.4.1 breaks recursive invocation with --print-directory [when adding to MAKEFLAGS]

2023-03-05 Thread Paul Smith
On Tue, 2023-02-28 at 19:02 -0600, Satish Balay via Bug reports and discussion for GNU make wrote: > This usage works with make-4.4 [and older versions] - but not 4.4.1 > > balay@p1 /home/balay/tmp > $ cat makefile > all: > @MAKEFLAGS="-j1 ${MAKEFLAGS}" ${MAKE} -f makefile hello > hello: >

Re: 4.4.1 breaks recursive invocation with --print-directory [when adding to MAKEFLAGS]

2023-03-05 Thread Satish Balay via Bug reports and discussion for GNU make
Thanks for all the suggestions. The code is not attempting to "change -j" - but have a "default" when the top-level is not invoked with '-j'. i.e: -'make' should use the default set in the makefile - make -j3' should use this value specified here [and ignore the default]. I'm reworking the code

whitespaces preceding backslash sometimes removed in POSIX mode

2023-03-05 Thread Arkadiusz Drabczyk
In the manual it says: "If the @code{.POSIX} special target is defined then backslash/newline handling is modified slightly to conform to POSIX.2: first, whitespace preceding a backslash is not removed and second, consecutive backslash/newlines are not condensed." but I cannot reproduce it with t