On Fri, Oct 9, 2020 at 11:11 AM Byrnes, Robert wrote:
>
> If I use this Makefile ...
>
>
> bash$ cat Makefile
> FOO := $(shell echo $(ENTRIES) ; )
> BAR := $(shell echo $(ENTRIES) )
>
> all:
> @echo FOO = $(FOO)
> @echo BAR = $(BAR)
>
> .PHONY: all
>
> Hm, interesting. I guess it's possible we are stripping out newlines before
> invoking the shell. I don't remember that being the case but it could be.
>
> I'm not exactly sure what your objective is ...
We use a make variable that can be set to a whitespace-separated list of
pathnames. The
On Fri, 2020-10-09 at 18:00 +, Byrnes, Robert wrote:
> [pid 144497] execve("/bin/sh", ["/bin/sh", "-c", "/bin/echo blartzblurfl ;
> "], 0x7ffd98ee6bc0 /* 72 vars */) = 0
Hm, interesting. I guess it's possible we are stripping out newlines
before invoking the shell. I don't remember that bei
> My suspicion is that it's a difference between your /bin/echo command and
> your shell's builtin echo command.
>
> In the first case (with the ";") because there's a special character in the
> command GNU make will run a shell like this:
>
>/bin/sh -c 'echo ... ; '
>
> and the shell's built
On Fri, 2020-10-09 at 15:03 +, Byrnes, Robert wrote:
> Why is the embedded whitespace removed in the first (FOO) case? It
> seems related to the semicolon shell metacharacter ...
My suspicion is that it's a difference between your /bin/echo command
and your shell's builtin echo command.
In t
