Re: "make -jN" requires mechanical changes to a Makefile

Henrik Carlqvist wrote: > If you really prefer to write rules which generates more than one target > the "right" way to avoid parallel make would be to add the .NOTPARALLEL > target in the Makefile. This way allows to turn off parallel make for a single Makefile. Indeed, this might be a better com

Re: "make -jN" requires mechanical changes to a Makefile

> In the current state, supporting parallel make requires extra work > for the maintainer. > > Or would you recommend that I add this snippet to the top-level > Makefile of all my projects? > > # This package does not support parallel make. > # So, turn off parallel execution (at least in GNU mak

Re: "make -jN" requires mechanical changes to a Makefile

Hi Paul, > This makefile should be written correctly, as: > > all : copy1 copy2 copy3 copy4 > > copy1: Makefile > install -c -m 644 Makefile copy1 > copy2: Makefile > install -c -m 644 Makefile copy2 > copy3: Makefile > install -c -m 644 Makefile copy3 > c

Re: "make -jN" requires mechanical changes to a Makefile

On Fri, 2019-05-10 at 22:49 +0200, Bruno Haible wrote: > But supporting parallel requires, in some cases, mechanical changes to a > Makefile. How about if GNU make was improved to not require me to make these > changes? > > Namely, consider this Makefile: >

"make -jN" requires mechanical changes to a Makefile

Hi, The GNU standards [1] say: "Try to make the build and installation targets, at least (and all their subtargets) work correctly with a parallel make." But supporting parallel requires, in some cases, mechanical changes to a Makefile. How about if GNU make was improved to not require me to

[bug #56301] Mandatory/Optional include files and pattern rule with multi-targets

URL: Summary: Mandatory/Optional include files and pattern rule with multi-targets Project: make Submitted by: masahiroy Submitted on: Fri 10 May 2019 04:33:49 PM UTC Severity: 3 - No

[bug #46013] Command overrides added to MAKEOVERRIDES are lost if there were no overrides in the command line

Follow-up Comment #3, bug #46013 (project make): It's disappointing that nothing seems to have happened to this bug since the original report 3.5 years ago. I ran into the same problem and it cost me quite a bit of time to understand what was going on (and would have costed even more if I didn't f