Update of bug #61805 (project make):
Status:None => Fixed
Assigned to:None => psmith
Open/Closed:Open => Closed
Operating System:
Update of bug #61864 (project make):
Status:None => Fixed
Assigned to:None => psmith
Open/Closed:Open => Closed
Operating System:
On Sat, 2022-02-05 at 11:24 +0100, Helge Kreutzmann wrote:
> I'm now reporting the errors for your project. If future reports
> should use another channel, please let me know.
This channel is fine, but please always do include the release of GNU
make that you're looking at when you submit changes
On Sun, 2022-02-06 at 17:12 -0500, Dmitry Goncharov wrote:
> 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 redirecte
On Sun, Feb 6, 2022 at 3:28 PM Paul Smith 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?
On Sun, 2022-02-06 at 15:21 -0500, Paul Smith wrote:
> I'm not sure this is correct. I will need to think about it.
I decided this was a bug and changed the behavior for the next release.
On Sun, Feb 06, 2022 at 03:21:39PM -0500, Paul Smith wrote:
> On Sun, 2022-02-06 at 20:18 +0300, Dmitry V. Levin wrote:
> > 4175643 write(2, "/bin/sh: bad-program: command no"...,
> > 40) = 40
> > 4175640 <... read resumed>"/bin/sh: bad-program: command no"..., 200) = 40
> > 4175640 read(5,
> >
On Sun, Feb 6, 2022 at 8:19 AM Dmitry V. Levin wrote:
>
> On Sun, Feb 06, 2022 at 11:23:03AM -0500, Paul Smith wrote:
> > OK, someone posted a question to SO and that led me to an hour or more
> > of banging my head against a wall trying to understand what's
> > happening... and I can't.
> >
> > T
On Sun, 2022-02-06 at 20:18 +0300, Dmitry V. Levin wrote:
> 4175643 write(2, "/bin/sh: bad-program: command no"...,
> 40) = 40
> 4175640 <... read resumed>"/bin/sh: bad-program: command no"..., 200) = 40
> 4175640 read(5,
> 4175643 +++ exited with 127 +++
> 4175640 <... read resumed>"", 160)
>> because this redirects the output of the bad-program, but it's the
>> shell printing the error not the program.
Dmitry's reply is more constructive but those strace arguments, all the pids
and pipe inodes, ow my head, so perhaps it's worth a simple demonstration that,
despite the undisputed t
On Sun, Feb 06, 2022 at 11:23:03AM -0500, Paul Smith wrote:
> OK, someone posted a question to SO and that led me to an hour or more
> of banging my head against a wall trying to understand what's
> happening... and I can't.
>
> The problem is that the user would like to invoke $(shell ...) and
>
OK, someone posted a question to SO and that led me to an hour or more
of banging my head against a wall trying to understand what's
happening... and I can't.
The problem is that the user would like to invoke $(shell ...) and
capture errors, even errors that the program being run doesn't exist.
T
On Sat, 05 Feb 2022 18:39:41 -0500
Paul Smith wrote:
> Nice work!
>
> On Sat, 2022-02-05 at 22:04 +, Sergei Trofimovich wrote:
> > Some high level TODOs:
>
> For this amount of change it's likely that you'll need to provide
> copyright assignment paperwork. Let me know if you'd like more
13 matches
Mail list logo
