public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: cygcheck failing to find file
Date: Fri, 16 Feb 2018 16:43:00 -0000	[thread overview]
Message-ID: <20180216164349.GB3122@calimero.vinschen.de> (raw)
In-Reply-To: <CAKqBF1gpENfzKjZdbP2RFPxPZpuHu6d7JPnAAJM3R+B5nQb3oQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1332 bytes --]

On Feb 15 14:58, Fergus Daly wrote:
> I have an executable (created in Cygwin) located on a mobile drive D:
> 
> $ ls -al /cygdrive/d/src/sc.exe
> -rwxr-xr-x 1 ferg dell 1426958 Jan 28 17:44 /cygdrive/d/src/sc.exe*
> $ cygcheck /cygdrive/d/src/sc.exe
> d:\src\sc.exe
> D:\consoleX\bin\cygwin1.dll
>  C:\Windows\system32\KERNEL32.dll
> <snip> # but it all works
> 
> Now omit the need for /cygdrive/ by writing /etc/fstab as
> none / cygdrive binary 0 0
> and re-start Cygwin.
> 
> $ ls -al /d/src/sc.exe
> -rwxr-xr-x 1 ferg dell 1426958 Jan 28 17:44 /d/src/sc.exe*
> $ cygcheck /d/src/sc.exe
> cygcheck: could not find '/d/src/sc.exe'
> 
> Why can't cygcheck find the file?
> (Particularly, when ls can. And so can, say, md5sum.)

Cygcheck is a native Windows executable and thus does not use Cygwin's
path handling (in contrast to md5sum, for instance).  Rather it uses a
home grown version and this in turn has a bug when checking the cygdrive
prefix against the incoming path.  Everything goes, just not '/' alone.

I pushed a fix and uploaded new developer snapshots to
https://cygwin.de/snapshots/

Please give them a try.


Thanks,
Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2018-02-16 16:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-15 14:58 Fergus Daly
2018-02-15 19:35 ` Andrey Repin
2018-02-16 16:43 ` Corinna Vinschen [this message]
2018-02-21  7:46 Fergus Daly
2018-02-21  8:50 ` Andrey Repin
2018-02-21  9:11   ` Corinna Vinschen
2018-02-21 20:50     ` Andrey Repin
2018-02-21  9:17   ` Fergus Daly
2018-02-21  9:53     ` Corinna Vinschen
2018-02-21  9:11 ` Corinna Vinschen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180216164349.GB3122@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).