From: Oskar Skog <oskar@oskog97.com>
To: cygwin@cygwin.com
Subject: Re: Couldn't compute FAST_CWD pointer
Date: Fri, 19 Aug 2022 15:23:27 +0300 [thread overview]
Message-ID: <d260a5b2-512f-824f-b573-5a146b4c31fe@oskog97.com> (raw)
In-Reply-To: <SA1P110MB1454D5B81E34ECFB6FD519DFA56C9@SA1P110MB1454.NAMP110.PROD.OUTLOOK.COM>
On 2022-08-19 15:11, Rick.Grape--- via Cygwin wrote:
> Below is the error I keep getting.
> I have re-installed latest Cygwin 2 times now, even deleted the old one but still getting this.
>
> M:\Projects>grep
> 0 [main] grep 137440 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>
That error message has been changed many years ago.
You either have multiple installations of Cygwin and are using the old
one, or you haven't installed the latest version (bad mirror?).
next prev parent reply other threads:[~2022-08-19 12:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-19 12:11 Rick.Grape
2022-08-19 12:15 ` cygwinautoreply
2022-08-19 12:23 ` Oskar Skog [this message]
2022-08-21 15:28 ` Erik Soderquist
-- strict thread matches above, loose matches on Subject: below --
2021-06-14 14:15 Olokunwolu, Elizabeth (FKN) - contr
2021-06-14 14:17 ` cygwinautoreply
2020-09-28 12:44 Alice Bilton
2020-09-28 12:45 ` cygwinautoreply
2020-09-28 12:51 ` Stephen John Smoogen
2020-09-28 12:55 ` Alice Bilton
2020-10-01 9:42 ` Andrey Repin
2018-05-03 18:20 emoctezuma
2018-05-03 18:24 ` Yaakov Selkowitz
2017-11-08 5:25 Ramirez Castro, Jesus Miguel
2017-11-08 8:42 ` Brian Inglis
[not found] <CAD1QJjUppq_ogX+VwM-H+0Fc=eM0k0YC8Mj5=imJBE3ceKBZ_g@mail.gmail.com>
2017-08-17 23:23 ` Fwd: " Richard Mateosian
2017-08-18 8:16 ` Csaba Raduly
2017-04-04 16:05 Tony An
2017-04-04 16:18 ` Douglas Coup
2017-04-04 23:05 ` Andrey Repin
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=d260a5b2-512f-824f-b573-5a146b4c31fe@oskog97.com \
--to=oskar@oskog97.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).