Re: shell function: confusing error when shebang incorrect

I have a feeling I may be treading over old ground here but wouldn't a simple solution be to simply abandon fast-path for explicit $(shell ...) invocations? After all, as Kirill says: > The documentation of the `shell` function pretty directly states that it will launch the shell, no exceptions,

Re: Dependency tracking not working on macOS

On 2022-10-09 15:43, Christoph Grüninger wrote: TMPDIR is also set, to an uncommon name (/var/folders/lr/5gw1xrv53h1b_9mjjvs2k1drgn/T/). Is that directory searchable, readable, writeable? Does its file system have enough free space? Any problems in that area could cause the symptoms

[PATCH] Fix bug in recipe line count overflow checking

Without this patch, the shell command: awk 'BEGIN { print "x:" for (i = 0; i < 65536; i++) printf "\techo %d\n", i} ' | make -f - incorrectly outputs only "make: 'x' is up to date." * src/commands.c (chop_commands): Report overflow in recipe line count when it occurs, as

Re: Dependency tracking not working on macOS

On 2022-10-09 15:17, Paul Smith wrote: On Sun, 2022-10-09 at 16:39 -0400, Zack Weinberg wrote: can I suggest that this kind of problem would be easier to troubleshoot if make printed the name of the temporary file that it could not fopen? In the current Git version, it does do this: ...

[bug #63172] Using --just-print, -n on a target that uses a multiline macro function will print as a single line

Update of bug #63172 (project make): Status:None => Not A Bug Open/Closed:Open => Closed ___ Follow-up Comment #1: This behavior is

Re: shell function: confusing error when shebang incorrect

On Sun, 2022-10-09 at 13:08 -0400, Kirill Elagin wrote: > On Sun, Oct 9, 2022 at 11:57 AM wrote: > > The interpretation of a bad shebang is platform-specific and has no > > single consistent interpretation. > > I am not convinced that platform-specific handling is not practical, > given that

Re: shell function: confusing error when shebang incorrect

On Sun, Oct 9, 2022 at 11:57 AM wrote: > The interpretation of a bad shebang is platform-specific and has no single > consistent interpretation. Some platforms will report EPERM, EACCESS, or > ENOENT. The error is not necessarily under bash or zsh control but could come > from exec[vpe]

RE: shell function: confusing error when shebang incorrect

On October 9, 2022 11:16 AM, Kirill Elagin wrote: >There is a bit of unexpected behaviour in the `shell` function (due to the >undocumented fact that it sometimes avoids actually calling the >shell): > >``` >$ cat Makefile >FOO:=$(shell ./foo.sh) > >$ cat foo.sh >#!/bin/ohno >echo hi > >$ make

shell function: confusing error when shebang incorrect

Hi, There is a bit of unexpected behaviour in the `shell` function (due to the undocumented fact that it sometimes avoids actually calling the shell): ``` $ cat Makefile FOO:=$(shell ./foo.sh) $ cat foo.sh #!/bin/ohno echo hi $ make make: ./foo.sh: No such file or directory make: *** No

[bug #63187] make: *** invalid shuffle mode: Invalid value: '0r'. Stop.

Update of bug #63187 (project make): Status:None => Not A Bug Open/Closed:Open => Closed ___ Follow-up Comment #3: This is a bug in the

[bug #63187] make: *** invalid shuffle mode: Invalid value: '0r'. Stop.

Follow-up Comment #2, bug #63187 (project make): I tried reverting a recent shuffle related commit: https://github.com/mirror/make/commit/a99378ebe46f5245ef1307c6a9834d19d57882d0 This didn't fix the error but it did change the error message. With revert: $ /home/buildroot/make/make BR2_JLEVEL=1

[bug #63187] make: *** invalid shuffle mode: Invalid value: '0r'. Stop.

Follow-up Comment #1, bug #63187 (project make): Looks like my account didn't get linked when I make this report, I'm the reporter. ___ Reply to this item at:

[bug #63187] make: *** invalid shuffle mode: Invalid value: '0r'. Stop.

URL: Summary: make: *** invalid shuffle mode: Invalid value: '0r'. Stop. Project: make Submitter: None Submitted: Sun 09 Oct 2022 08:53:01 AM UTC Severity: 3 - Normal