> But what
> should really happen is make should re-try the slow path if the fast
> path fails with a "command not found" error... then we wouldn't have to
> keep adding non-standard built-ins to these lists.
I’m wondering if this ever happened, and if there’s an issue tracking work on
this!
Che
On 11/18/17, Paul Smith wrote:
> On Tue, 2017-11-07 at 13:43 -0500, Nick Bowler wrote:
>> Is this behaviour intended? I noticed the manual says "make may take
>> shortcuts that do not affect the results" but in this instance a change
>> in results is definitely observed.
>
> Well, technically "co
On Tue, 2017-11-07 at 13:43 -0500, Nick Bowler wrote:
> Is this behaviour intended? I noticed the manual says "make may take
> shortcuts that do not affect the results" but in this instance a change
> in results is definitely observed.
Well, technically "command" is not a valid POSIX shell built-
Hi,
GNU make (version 4.2.1) appears to have some magic to bypass shell
invocations when running commands. I guess this usually helps with
performance but I noticed a failure when using the 'command' shell
builtin. For example:
% cat >Makefile <<'EOF'
foo:
command -v ls
.PHONY: fo
