> "PS" == Paul Smith writes:
PS> I think the behavior you're seeing is due to a bug in the older version
PS> of gnulib that was used to build your version of GNU make, which as
PS> since been fixed.
OK. I hope so. P.S.,
$ make --version
GNU Make 4.3
Built for x86_64-pc-linux-gnu
Copyright
On Tue, 2021-04-27 at 05:10 +0800, 積丹尼 Dan Jacobson wrote:
> > > > > > "PS" == Paul Smith writes:
> PS> In the second example, the "Z" command is by itself so it's
> "simple" so
> PS> make uses its fast path solution, which is to fork and exec "Z"
> PS> directly without a shell. Thus you get an
> "PS" == Paul Smith writes:
PS> In the second example, the "Z" command is by itself so it's "simple" so
PS> make uses its fast path solution, which is to fork and exec "Z"
PS> directly without a shell. Thus you get an error from make.
OK, but please have the message distinguish like these
Follow-up Comment #13, bug #47880 (project make):
> > My opinion is that the users should not have to know this detail.
> I didn't realize you were wearing your 'user' hat!
My bad. By "users" here (and in other places) i meant make users, people who
write makefiles. In other words, when a user
Follow-up Comment #12, bug #47880 (project make):
> > include $(CURDIR)/foo.mk
>
> This indeed suppresses the lookup.
>
> My opinion is that the users should not have to know this detail.
I didn't realize you were wearing your 'user' hat! To me, this is a problem
ideally for the author to
On Mon, 2021-04-26 at 06:25 +0800, Dan Jacobson wrote:
> $ make B
> :; Z
>
> /bin/sh: line 1: Z: command not found
> make: *** [Makefile:2: B] Error 127
>
> $ make C
> :
> Z
>
> make: Z: No such file or directory
> make: *** [Makefile:5: C] Error 127
>
> So we see that "the effect is the
(info "(make) Rule Syntax") says
The first recipe line may appear on the line after the
prerequisites, with a tab character, or may appear on the same line,
with a semicolon. Either way, the effect is the same.
However,
$ cat Makefile
B:; :; Z
C:
:
Z
$ make B
Follow-up Comment #11, bug #47880 (project make):
> Can you use this?:
> include $(CURDIR)/foo.mk
This indeed suppresses the lookup.
My opinion is that the users should not have to know this detail. The behavior
should preferably be optimial for the most common scenarios.
Also, most (as far as
