From:	cgf AT cygnus DOT com (Christopher G. Faylor)
Subject:	Re: More on relative pathname
16 Jan 1999 04:14:28 GMT :
Message-ID:	<77p3n4$l8p$1@cronkite.cygnus.com>
References:	<001d01be3f17$9db783c0$bee2e183 AT gtw_nt DOT fnal DOT gov> <369E5416 DOT 3498DC6B DOT cygnus DOT gnu-win32 AT cityweb DOT de>
X-Newsreader:	trn 4.0-test63 (15 March 1998)

In article <369E5416 DOT 3498DC6B DOT cygnus DOT gnu-win32 AT cityweb DOT de>,
Corinna Vinschen <corinna DOT vinschen AT cityweb DOT 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 AT cygnus DOT com
http://www.cygnus.com/

- Raw text -