Poor messages when the '#!' file isn't found

$ echo \#!/usr/bin/python > k $ chmod +x k $ ./k bash: ./k: cannot execute: required file not found Bash should really mention what file it is talking about. $ echo 'x:k; ./$<' > Makefile $ make ./k make: ./k: No such file or directory make: *** [Makefile:1: x] Error 127 $ ls ./k ./k Make is wor

Re: Poor messages when the '#!' file isn't found

On Fri, Jun 14, 2024 at 02:13:37AM +0800, Dan Jacobson wrote: > $ echo \#!/usr/bin/python > k > $ chmod +x k > $ ./k > bash: ./k: cannot execute: required file not found > > Bash should really mention what file it is talking about. Bash doesn't KNOW what file is missing. All it knows is that the

Re: Poor messages when the '#!' file isn't found

On Fri, 14 Jun 2024 at 06:13, Dan Jacobson wrote: > ./k > make: ./k: No such file or directory > This is a problem with the POSIX spec for the execve system call and its obligatory return codes. "No such file or directory" is arguably the correct message to show when the kernel returns the ENOE