public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Windows 10 Insider Preview OS Build 15007.1000: Couldn't compute FAST_CWD pointer
Date: Tue, 17 Jan 2017 12:13:00 -0000	[thread overview]
Message-ID: <20170117121251.GB5159@calimero.vinschen.de> (raw)
In-Reply-To: <CAK-n8j4YVv4b2w8UZ-YyeVUuRSYmK87zF1+UERLKCGO0dbGutw@mail.gmail.com>

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

On Jan 17 03:12, Jim Reisert AD1C wrote:
> I just upgraded my Windows 10 Home 64-bit installation to the latest
> Windows Insider preview version:
> 
>     Version: 1607
>     OS Build:  15007.1000
> 
> I'm now getting this warning from Cygwin, but only in a CMD window
> (not XWin).  It doesn't seem to affect anything negatively.
> cygcheck.out attached (I got the FAST_CWD warning three times during
> the generation of the file):
> 
> C:\Users\jjrei>uname -a
> 
> Cygwin WARNING:
>   Couldn't compute FAST_CWD pointer.  This typically occurs if you're using
>   an older Cygwin version on a newer Windows.  Please update to the latest
>   available Cygwin version from https://cygwin.com/.  If the problem persists,
>   please see https://cygwin.com/problems.html

Try the latest developer snapshot from https://cygwin.com/snapshots/


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: 819 bytes --]

  reply	other threads:[~2017-01-17 12:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-17 10:12 Jim Reisert AD1C
2017-01-17 12:13 ` Corinna Vinschen [this message]
2017-01-20 14:38   ` Jim Reisert AD1C
2017-01-20 15:45     ` Csaba Raduly
2017-01-20 17:39       ` Jim Reisert AD1C
2017-01-21 15:46       ` Jim Reisert AD1C

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=20170117121251.GB5159@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).