[bug #62706] Restrict second expansion to targets which are being built.

Update of bug #62706 (project make): Status:None => Fixed Open/Closed:Open => Closed Fixed Release:None => SCM

Re: [bug #62840] make --version in pipe return SIGPIPE

On Sat, 30 Jul 2022 13:26:46 -0400 (EDT) Martin Dorey wrote: > Follow-up Comment #2, bug #62840 (project make): > > Just for completeness or academic interest, then, this makes it happen > reliably for me: > > > set -o pipefail; { ruby -we '$stdout.write("x" * 4096)'; make --version; } | >

[bug #62840] make --version in pipe return SIGPIPE

Follow-up Comment #2, bug #62840 (project make): Just for completeness or academic interest, then, this makes it happen reliably for me: set -o pipefail; { ruby -we '$stdout.write("x" * 4096)'; make --version; } | head -n1; echo $? That behaved the same all the way back to make-3.81. This

[bug #62840] make --version in pipe return SIGPIPE

Follow-up Comment #1, bug #62840 (project make): I'm not convinced that this is a bug. First, it's highly timing-dependent: when I tried it it didn't fail: $ make --version | head -n1 GNU Make 4.3 $ echo $? 0 Second, you can get similar behavior from other commands; you just have to be sure

Re: New feature: Post-requisites

On Mon, 2022-07-25 at 09:06 +, Edward Welbourne wrote: > On 7/22/22 16:20, Paul Smith wrote: > > > So, after all the "normal" goal targets were completed make would > > > proceed to run any "extra" goal targets that were added as part > > > of the processing of the "normal" goal targets.  Then

[bug #62840] make --version in pipe return SIGPIPE

URL: Summary: make --version in pipe return SIGPIPE Project: make Submitter: katchov Submitted: Sat 30 Jul 2022 04:24:33 PM UTC Severity: 3 - Normal Item Group: