When introducing the new .WAIT special target in some of my
makefiles, I noticed a surprising (to me) behaviour, as shown in
this example using a simple ad-hoc single-stepping mechanism
(not quite my actual use case, but sufficient for this example):
% cat Makefile
all: step1 .WAIT pause .WAIT ste
On Tue, 2022-11-01 at 14:15 +0100, Frank Heckenbach wrote:
> So "pause" is run only once. Now, I suppose that's as it's supposed
> to be (by comparison with the same rule without ".WAIT"), and I
> don't expect you to change anything about it, so that's basically
> just for information to anyone who
Paul Smith wrote:
> On Tue, 2022-11-01 at 14:15 +0100, Frank Heckenbach wrote:
> > So "pause" is run only once. Now, I suppose that's as it's supposed
> > to be (by comparison with the same rule without ".WAIT"), and I
> > don't expect you to change anything about it, so that's basically
> > just
On Tue, 2022-11-01 at 22:51 +0100, Frank Heckenbach wrote:
> That's why I only suggested a warning since it may be un expected
> (especially with ".WAIT") or unintended (even in your example at the
> end, why would one put "pause" twice intentionally).
I see. We can't do this; there are tons of w
Version is not being displayed on FreeBSD.
[kandy@ ~/a]$ make --version
>
>
$< and $^ do not seem to work on FreeBSD.
[kandy@ ~/a]$ cat Makefile
> a:
> echo "0:"
> echo $@
> echo "1:"
> echo $<
> echo "2:"
> echo $^
>
> :
>
> .SILENT : a
> .PHONY : a
>
[kandy@ ~/a]$ make
> 0:
> a
> 1:
>
> 2:
>
>
