Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -g -O2
-fdebug-prefix-map=/build/bash-Smvct5/bash-5.0=.
-fstack-protector-strong -Wformat -Werror=format-security -Wall
-Wno-parentheses -Wno-format-security
uname
e R. Worley wrote:
Chet Ramey writes:
On 5/26/22 2:27 PM, AA via Bug reports for the GNU Bourne Again SHell wrote:
When a user attempts to execute an executable that is not
recognized as an executable by the system, the generated error is "No such
file or directory"
In this case,
ice if there isn’t a
technical solution to disambiguate the actual error condition.
My nezt step was going to be to find the source, and check where the
string is generated or looked ip.
A.
On May 29, 2022, at 4:34 AM, Martin D Kealey
wrote:
On Sun, 29 May 2022, 06:56 AA via Bug report
Neigh!
;)
On 6/3/22 7:06 AM, Chet Ramey wrote:
On 5/29/22 10:54 AM, AA via Bug reports for the GNU Bourne Again SHell
wrote:
The horse is almost dead.
It's in the ground.
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -g -O2
-fdebug-prefix-map=/build/bash-Smvct5/bash-5.0=.
-fstack-protector-strong -Wformat -Werror=format-security -Wall
-Wno-parentheses -Wno-format-security
uname
Greg: I included a link to the github. There are only 3 PRs, one of
which is mine. That's why I was suspicious it's the wrong place.
Here is a link to the actual patch:
https://github.com/gitGNU/gnu_bash/pull/5/files
Robert: Yes, I meant the section of "man bash" that discusses the
builtins
