From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: cygcheck failing to find file
Date: Wed, 21 Feb 2018 09:11:00 -0000 [thread overview]
Message-ID: <20180221091053.GO3417@calimero.vinschen.de> (raw)
In-Reply-To: <3510016687.20180221114620@yandex.ru>
[-- Attachment #1: Type: text/plain, Size: 1083 bytes --]
On Feb 21 11:46, Andrey Repin wrote:
> Greetings, Fergus Daly!
>
> >>> Cygcheck is a native Windows executable .. ..
> >>> I pushed a fix and uploaded new developer snapshots to
> >>> https://cygwin.de/snapshots/
> >>> Please give them a try.
>
> > I tried your link above but got "HTTP 404 Not found".
> > Just in case this was your intention I tried the latest cygwin1.dll
> > snapshot from
> > https://cygwin.com/snapshots/
> > being 20180216 but still got
> >> $ cygcheck /d/src/sc.exe
> >> cygcheck: could not find '/d/src/sc.exe'
>
> > I just tried the 20180220 snapshot; but still get
> >> $ cygcheck /d/src/sc.exe
> >> cygcheck: could not find '/d/src/sc.exe'
>
> For the third time, cygcheck is no Cygwin application, and unaware of Cygwin
> paths.
> Please give it native Windows paths.
Incorrect. Yes, cygcheck is a native Windows app, NO, you don't
have to use Windows paths.
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 --]
next prev parent reply other threads:[~2018-02-21 9:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-21 7:46 Fergus Daly
2018-02-21 8:50 ` Andrey Repin
2018-02-21 9:11 ` Corinna Vinschen [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2018-02-15 14:58 Fergus Daly
2018-02-15 19:35 ` Andrey Repin
2018-02-16 16:43 ` 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=20180221091053.GO3417@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).