Re: Parallel Build, but Not for the Command-Line Targets.

2014-08-27 Thread Ralph Corderoy
Hi don, > That definitely makes sense, and I was quite shocked to discover this > problem. ("make -j clean all" does /what/?!) Me too. :-) > I thought a temporal prerequisite might be the solution. Like a weak dependency, perhaps check?: all > I claim that a requirement for ordering on t

Re: Parallel Build, but Not for the Command-Line Targets.

2014-08-26 Thread dprovan
nt for ordering on the command line is caused, for the most part, because the user knows what logical order the makefile needs, and the makefile cannot express the requirement for itself. -don provan -- View this message in context: http://gnu-make.2324884.n4.nabble.com/Parallel-Build-but-No

Re: Parallel Build, but Not for the Command-Line Targets.

2014-08-26 Thread Eli Zaretskii
> Date: Tue, 26 Aug 2014 15:03:34 +0200 > From: Reinier Post > > Maybe an interesting use case could be shells that don't support &&? There aren't any. ___ Bug-make mailing list Bug-make@gnu.org https://lists.gnu.org/mailman/listinfo/bug-make

Re: Parallel Build, but Not for the Command-Line Targets.

2014-08-26 Thread Reinier Post
On Mon Aug 25 10:40:39 2014, ra...@inputplus.co.uk (Ralph Corderoy) wrote: > Hi Reinier, > > > > Yes, but it's an idiomatic one, oft suggested; "Unpack and run > > > `./configure && make all check install'". > > > > I don't get it. What is wrong with > > > > make -sj clean; make -sj all; mak

Re: Parallel Build, but Not for the Command-Line Targets.

2014-08-25 Thread Ralph Corderoy
Hi Reinier, > > Yes, but it's an idiomatic one, oft suggested; "Unpack and run > > `./configure && make all check install'". > > I don't get it. What is wrong with > > make -sj clean; make -sj all; make -sj check; make -sj install That doesn't do the same thing; `make all check install' st

Re: Parallel Build, but Not for the Command-Line Targets.

2014-08-25 Thread Reinier Post
On Sun Aug 24 12:33:41 2014, ra...@inputplus.co.uk (Ralph Corderoy) wrote: > Hi Paul, > > > > It seems a design flaw that I must > > > > > > make -sj clean && make -sj all && make -sj check && > > > make -sj install > > > > Well, that's because you're only considering this use-case, > >

Re: Parallel Build, but Not for the Command-Line Targets.

2014-08-24 Thread Ralph Corderoy
Hi Paul, > > It seems a design flaw that I must > > > > make -sj clean && make -sj all && make -sj check && > > make -sj install > > Well, that's because you're only considering this use-case, Yes, but it's an idiomatic one, oft suggested; "Unpack and run `./configure && make all check

Re: Parallel Build, but Not for the Command-Line Targets.

2014-08-23 Thread Paul Smith
On Sat, 2014-08-23 at 16:25 +0100, Ralph Corderoy wrote: > It seems a design flaw that I must > > make -sj clean && make -sj all && make -sj check && make -sj install Well, that's because you're only considering this use-case, where we know the context and it's clear that building them in par

Parallel Build, but Not for the Command-Line Targets.

2014-08-23 Thread Ralph Corderoy
Hi, I find it odd that -j breaks the idiomatic `make clean all check install'. Consider $ cat makefile #! /usr/bin/make -f SHELL = /bin/bash all: sleep 0.$$((RANDOM % 10)) && echo all clean:: sleep 0.$$((RANDOM % 10)) && echo clean check::