On 26 July 2017 at 23:58, Ken Moffat <[email protected]> wrote:
> With expat-2.2.2 the tests are invoked from a run.sh script. > > But that script starts: > #! /usr/bin/env bash > > (I didn't know you could put a space after the shebang). > >From the excellent "Classic Shell Scripting" by Robbins and Beebe, the form #! /bin/sh - is suggested. With the following caveats:- "The POSIX standard leaves the behaviour of #! as 'unspecified'." "On antique systems that don't have #! interpretation in the kernel, some shells will do it themselves, and they may be picky about the presence or absence of white space characters between the #! and the name of the interpreter." "Don't put any trailing white space after an option, if present. It will get passed along to the invoked program along with the option." "The bare option - says that there are no more shell options; this is a security feature to prevent certain kinds of spoofing attacks." Having read that some years ago I always add the - option to my scripts as a matter of course. Richard
-- http://lists.linuxfromscratch.org/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
