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
The discussion so far has been based on the idea that the user is expressing
an order on the command line and will be surprised if that order is not
followed. That definitely makes sense, and I was quite shocked to discover
this problem. ("make -j clean all" does /what/?!)
But when I ran into this
> 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
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
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
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,
>
>
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
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
