This is the mail archive of the cygwin-developers@sources.redhat.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

path bug in cygcheck?


This is probably very minor, but 'cygcheck program' behaves strangely,
at least when I use it:

> $ echo $PATH
> /usr/bin:/usr/local/xemacs-21.1.7/bin:/usr/local/bin:/c/jdk1.3/bin:/c/WINNT/system32:/c/WINNT:/c/NTRESKIT

Note the presence of SysDir.

> $ type -a cmd
> cmd is /c/WINNT/system32/cmd

Fine, but:

> $ cygcheck cmd
> Error: could not find cmd

In fact, it seems to not find anything in SysDir:

> $ type -a ftp
> ftp is /usr/bin/ftp
> ftp is /usr/local/bin/ftp
> ftp is /c/WINNT/system32/ftp

but:

> $ cygcheck ftp
> Found: C:\cygwin\bin\ftp.exe
> Found: C:\usr\local\bin\ftp.exe
> C:\cygwin\bin\ftp.exe
>   C:\cygwin\bin\cygwin1.dll
>     C:\WINNT\System32\KERNEL32.dll
> 	C:\WINNT\System32\ntdll.dll

(nothing about C:\WINNT\System32\ftp.exe)

I'm looking at the source now, but perhaps it's a known problem or by
design.

It came up because I was hoping to update the FAQ entry "How can I
find out which dlls are needed by an executable?" with advice on using
cygcheck for this.  (A lot less verbose than objdump -p if that's all
you need.)

Cheers,
David


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]