From: Andrey Repin <anrdaemon@yandex.ru>
To: James <james.kuypers@gmail.com>, cygwin@cygwin.com
Subject: Re: 1 [main] bash 17336 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please report this problem to the public mailing list cygwin@cygwin.com
Date: Mon, 4 Apr 2022 10:29:01 +0300 [thread overview]
Message-ID: <70465615.20220404102901@yandex.ru> (raw)
In-Reply-To: <CAJ8-=37KvDyAHT+kTtn1N7LYQetsDoSgOu3WcrX4sfyU_r7U8g@mail.gmail.com>
Greetings, James!
> Never mind I'd say. I got the error when launching
> C:\Appz\Cygwin\Cygwin.bat
> Which is just
> @echo off
> C:
> chdir C:\Appz\Cygwin\bin
> bash --login -i
> If however I run
> C:\cygwin64\bin\mintty.exe
> It works fine.
This means you have two different Cygwin versions installed.
If you never use the other one, I strongly suggest removing it, as an unused
and unmaintained program is often a good target for various troublemakers.
And that other version of Cygwin you have IS unmaintained, judging by the
error you receive from it (which was fixed over a decade ago).
> On Sat, Apr 2, 2022 at 8:28 AM James <james.kuypers@gmail.com> wrote:
>> Hi there,
>>
>>
>> I just got that error message, asking me to report it here.
>>
>> 1 [main] bash 17336 find_fast_cwd: WARNING: Couldn't compute
>> FAST_CWD pointer. Please report this problem to the public mailing list
>> cygwin@cygwin.com
>>
>> Not sure if it's interesting?
--
With best regards,
Andrey Repin
Monday, April 4, 2022 10:26:57
Sorry for my terrible english...
prev parent reply other threads:[~2022-04-04 7:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-02 6:28 James
2022-04-02 6:31 ` cygwinautoreply
2022-04-02 6:32 ` James
2022-04-02 7:37 ` Backwoods BC
2022-04-02 10:38 ` Eliot Moss
2022-04-02 14:40 ` Brian Inglis
2022-04-02 6:31 ` James
2022-04-04 7:29 ` Andrey Repin [this message]
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=70465615.20220404102901@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=cygwin@cygwin.com \
--cc=james.kuypers@gmail.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).