Re: Bug in $(shell ...) I can't understand

[Dmitry Goncharov]

On Sun, Feb 6, 2022 at 3:28 PM Paul Smith <psmith@gnu.org> wrote:
> Oh.  I see the problem.  If the shell exits with an exit code of 127
> then make's shell function assumes that it failed because the sub-
> process was not found, and it actually writes its output to stderr!!

This behavior is correct, is not it?

$ cat makefile
SHELL:=/badpath/bash
value:=$(shell echo hello world)
all: ; $(info $(value))
$ make >/dev/null
make: /badpath/bash: No such file or directory
$

stdout is redirected to /dev/null, but the user still wants to see
errors. Is not this scenario what stderr was invented for?

On Sun, Feb 6, 2022 at 4:48 PM Paul Smith <psmith@gnu.org> wrote:
> I decided this was a bug and changed the behavior for the next release.

What is the new behavior?

regards, Dmitry