Re: cygcheck bug: symlinks with unix paths are wrongly resolved

2010-10-22 Thread Daniel Barclay
Andrey Repin wrote: Greetings, Csaba Raduly! ... The API can handle "/" as the path separator, but cmd.exe can't. You're seriously wrong... How? (Which part is wrong?) The Start menu's Run... command accepts forward slashes, and cmd.exe parses unquoted forward slashes as parameter delimi

Re: cygcheck bug: symlinks with unix paths are wrongly resolved

2010-10-21 Thread Andrey Repin
Greetings, Csaba Raduly! > On Thu, Oct 21, 2010 at 4:46 AM, Andrey Repin wrote: >> >> Not to mention, the Windows itself don't see much of a difference between "/" >> and "\" in path. (where it see, it is a bug). > The API can handle "/" as the path separator, but cmd.exe can't. You're seriousl

Re: cygcheck bug: symlinks with unix paths are wrongly resolved

2010-10-21 Thread Csaba Raduly
On Thu, Oct 21, 2010 at 4:46 AM, Andrey Repin wrote: > > Not to mention, the Windows itself don't see much of a difference between "/" > and "\" in path. (where it see, it is a bug). The API can handle "/" as the path separator, but cmd.exe can't. -- GCS a+ e++ d- C++ ULS$ L+$ !E- W++ P+++$ w++

Re: cygcheck bug: symlinks with unix paths are wrongly resolved

2010-10-20 Thread Christopher Faylor
On Thu, Oct 21, 2010 at 06:46:16AM +0400, Andrey Repin wrote: >Greetings, Christopher Faylor! > >>>[snip...] a...@dstar ~ $ ln -s `which cmd.exe` cmd.exe a...@dstar ~ $ cygcheck ./cmd.exe -> D:\OTHERBIN\cygwin\cygdrive\d\WINDOWS\system32\cmd.exe cygcheck: could

Re: cygcheck bug: symlinks with unix paths are wrongly resolved

2010-10-20 Thread Andrey Repin
Greetings, Christopher Faylor! >>[snip...] >>> a...@dstar ~ >>> $ ln -s `which cmd.exe` cmd.exe >>> >>> a...@dstar ~ >>> $ cygcheck ./cmd.exe >>> -> D:\OTHERBIN\cygwin\cygdrive\d\WINDOWS\system32\cmd.exe >>> cygcheck: could not find './cmd.exe' >> >>cygcheck is not a cygwin application, it's a

Re: cygcheck bug: symlinks with unix paths are wrongly resolved

2010-10-20 Thread Christopher Faylor
On Wed, Oct 20, 2010 at 07:46:05PM -0400, Rolf Campbell wrote: >On 2010-10-19 19:17, Arseny Slobodyuk wrote: >[snip...] >> a...@dstar ~ >> $ ln -s `which cmd.exe` cmd.exe >> >> a...@dstar ~ >> $ cygcheck ./cmd.exe >> -> D:\OTHERBIN\cygwin\cygdrive\d\WINDOWS\system32\cmd.exe >> cygcheck: could no

Re: cygcheck bug: symlinks with unix paths are wrongly resolved

2010-10-20 Thread Rolf Campbell
On 2010-10-19 19:17, Arseny Slobodyuk wrote: [snip...] a...@dstar ~ $ ln -s `which cmd.exe` cmd.exe a...@dstar ~ $ cygcheck ./cmd.exe -> D:\OTHERBIN\cygwin\cygdrive\d\WINDOWS\system32\cmd.exe cygcheck: could not find './cmd.exe' cygcheck is not a cygwin application, it's a native windows ap

Re: cygcheck bug

2006-02-08 Thread Corinna Vinschen
On Feb 7 23:21, Eric Blake wrote: > $ uname -a > CYGWIN_98-4.10 bedroom 1.5.19(0.150/4/2) 2006-01-20 13:28 i686 Cygwin > $ cd /bin > $ cygcheck ./bash > .\.\.\.\.\ - Cannot open > $ cygcheck ./bash.exe > .\bash.exe > .\cygwin1.dll > ... I've checked in a fix. Thanks, Corinna -- Corinna Vins

Re: cygcheck bug

2006-02-07 Thread Eric Blake
> > $ uname -a > > CYGWIN_98-4.10 bedroom 1.5.19(0.150/4/2) 2006-01-20 13:28 i686 Cygwin > > $ cd /bin > > $ cygcheck ./bash > > .\.\.\.\.\ - Cannot open > > $ cygcheck ./bash.exe > > .\bash.exe > > .\cygwin1.dll > > ... > > FWIW, WFM: > > $ cygcheck --version > cygcheck version 1.74 > System C

Re: cygcheck bug

2006-02-07 Thread Igor Peshansky
On Tue, 7 Feb 2006, Eric Blake wrote: > $ uname -a > CYGWIN_98-4.10 bedroom 1.5.19(0.150/4/2) 2006-01-20 13:28 i686 Cygwin > $ cd /bin > $ cygcheck ./bash > .\.\.\.\.\ - Cannot open > $ cygcheck ./bash.exe > .\bash.exe > .\cygwin1.dll > ... FWIW, WFM: $ uname -svr CYGWIN_NT-5.1 1.5.20(0.153/4/

Re: cygcheck bug when listing services (Was Re: Parallel writes to a single FIFO do not queue, and deadlock cygwin)

2005-12-06 Thread Yitzchak Scott-Thoennes
On Mon, Dec 05, 2005 at 09:40:01AM -0500, Igor Pechtchanski wrote: > Running cygcheck under strace shows that after listing all the available > services, it invokes "cygrunsrv --query grunsrv.exe --list", which results > in the above message. I think this may be because the output of > "cygrunsrv