From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Cc: "Srikantaiah, Jagadesh" <Jagadesh.Srikantaiah@harman.com>
Subject: Re: Find_fast_cwd : warning
Date: Thu, 18 Jun 2020 13:57:44 -0600 [thread overview]
Message-ID: <33176142-efd3-2af0-d485-043cdffae90d@SystematicSw.ab.ca> (raw)
In-Reply-To: <8f428ca8c75841699d0e89a16b91a394@HIBDWSMB05.ad.harman.com>
Your Cygwin version does not support your Windows version:
you must upgrade Cygwin and all packages using Cygwin setup;
see:
https://cygwin.com/faq.html#faq.using.fixing-find_fast_cwd-warnings
and choose:
https://cygwin.com/setup-x86_64.exe
or:
https://cygwin.com/setup-x86.exe
On 2020-06-18 08:23, Srikantaiah, Jagadesh via Cygwin wrote:
> I still finding the same warnings , could you let me what's other possibility to resolve this issue
>> I am facing below warning many times when I am using
>> cygwin\lib\gcc\i686-pc-cygwin\4.8.3 ..please do me know what is the
>> solution for this issue
>> 1 [main] sh 18352 find_fast_cwd: WARNING: Couldn't compute FAST_CWD
>> pointer. Please report this problem to the public mailing list
>> cygwin@cygwin.com<mailto:cygwin@cygwin.com>
> https://cygwin.com%/faq.html#faq.using.fixing-find_fast_cwd-warnings
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in IEC units and prefixes, physical quantities in SI.]
next prev parent reply other threads:[~2020-06-18 19:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-16 3:53 Srikantaiah, Jagadesh
2020-06-16 5:01 ` cygwinautoreply
2020-06-18 14:23 ` [EXTERNAL] " Srikantaiah, Jagadesh
2020-06-18 19:57 ` Brian Inglis [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-05-05 18:10 Error Maxime M
2018-05-05 18:23 ` find_fast_cwd WARNING Brian Inglis
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=33176142-efd3-2af0-d485-043cdffae90d@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=Jagadesh.Srikantaiah@harman.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).