Mail Archives: cygwin/1999/01/14/20:04:55
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".
- Raw text -