From: corinna DOT vinschen AT cityweb DOT de (Corinna Vinschen)
Subject: Re: More on relative pathname
14 Jan 1999 20:04:55 -0800
Message-ID: <369E5416.3498DC6B.cygnus.gnu-win32@cityweb.de>
References: <001d01be3f17$9db783c0$bee2e183 AT gtw_nt DOT fnal DOT gov>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: "Gordon Watts (Brown University)" <gwatts AT fnal DOT gov>, gnu-win32 AT cygnus DOT com

Gordon Watts (Brown University) wrote:
> 
> Taking the suggestion of Earnie Boyd, I replaced the #!/bin/sh in my sample
> script with #!/bin/bash. Now the relative path names work fine.
> Unfortunately, I can't make this change in all the code I'm running (this is
> a port with a common source base), so I still need to get sh to work
> correctly, but it is an interesting data point, none the less. Would this
> indicate a problem in sh or in the cygwin dll below it? I guess it depends
> upon how sh invokes sub-shells.
> 
>         Cheers,
>                 Gordon.

Copy bash.exe to /bin/sh.exe and it will work, without changing the script.

Regards,
Corinna


-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".