This is the mail archive of the
cygwin@sourceware.cygnus.com
mailing list for the Cygwin project.
Re: mysterious bash problem
- To: Earnie Boyd <earnie_boyd at hotmail dot com>
- Subject: Re: mysterious bash problem
- From: Fergus Henderson <fjh at cs dot mu dot OZ dot AU>
- Date: Thu, 15 Jan 1998 12:12:37 +1100
- Cc: Ulrich dot Lauther at mchp dot siemens dot de, gnu-win32 at cygnus dot com
- References: <19980113142530.20840.qmail@hotmail.com>
On 13-Jan-1998, Earnie Boyd <earnie_boyd@hotmail.com> wrote:
>
> Ulrich Lauther <ulrich.lauther@mchp.siemens.de> writes:
> >
> >Let foo be a valid shell script (starting with a ":" in the first line,
> >BTW):
>
> To execute a script the first non-blank line must begin with
>
> #! /bin/sh
>
> where /bin/sh is the path and shell you want to execute.
I think you're missing some history. Using `:' in the first line to
identify a Bourne shell script (as opposed to `#', for a C-shell script)
actually predates the `#!' convention.
If gnu-win32 doesn't support execution of shell scripts starting with
`:', then this is a bug in gnu-win32. It works fine with other Unix
systems, including Linux.
In any case, the form of the error message
> >bash.exe: ./foo: (null)
is clearly a bug.
--
Fergus Henderson <fjh@cs.mu.oz.au> | "I have always known that the pursuit
WWW: <http://www.cs.mu.oz.au/~fjh> | of excellence is a lethal habit"
PGP: finger fjh@128.250.37.3 | -- the last words of T. S. Garp.
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".