More on relative pathname

[Christopher G. Faylor]

In article <369E5416.3498DC6B.cygnus.gnu-win32@cityweb.de>,
Corinna Vinschen <corinna.vinschen@cityweb.de> wrote:
>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.

At the expense of substantial performance penalty.

It's a cygwin bug, fixed in the latest snapshot.
-- 
cgf@cygnus.com
http://www.cygnus.com/
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".