From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com, evilworld015@gmail.com
Subject: Re: Report
Date: Fri, 30 Mar 2018 16:18:00 -0000 [thread overview]
Message-ID: <34e17a06-9ffd-6aec-dc98-a385f9210173@gmail.com> (raw)
In-Reply-To: <437B07D1-9072-40AF-8F10-C755D0C2EB98@solidrocksystems.com>
On 30/03/2018 00:40, Vince Rice wrote:
>> On Mar 29, 2018, at 5:36 PM, Erik Soderquist wrote:
>>
>> On Thu, Mar 29, 2018 at 5:33 PM, Evil World wrote:
>>> 3 [main] john 7512 find_fast_cwd: WARNING: Couldn't compute FAST_CWD
>>> pointer. Please report this problem
>>
>>
>> We need more detail to be able to do anything... please refer to the
>> instuctions at https://cygwin.com/problems.html
>
>
> In that particular case, we don't. To the OP: see the FAQ.
For the first "evil" sender that unlikely is on this mailing list
https://cygwin.com/faq.html#faq.using.fixing-find_fast_cwd-warnings
Your message is coming from the first version and this means
you are using a third party tool/software that has embedded an
old an obsolete version of cygwin1.dll.
We have no clue of what tool is as you have not mentioned.
Ask them to update their distribution. We can
> (I'm dying to know why we're having a rash of these the last few months.)
We are a very popular POSIX layer, and people around make tools and
forgot to update them...
Regards
Marco
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2018-03-30 11:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-29 22:36 Report Evil World
2018-03-29 22:40 ` Report Erik Soderquist
2018-03-29 23:11 ` Report Vince Rice
2018-03-30 16:18 ` Marco Atzeri [this message]
2019-03-28 18:34 Report Jirka
2019-03-28 18:43 ` Report Björn Stabel
2019-03-28 18:52 ` Report Marco Atzeri
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=34e17a06-9ffd-6aec-dc98-a385f9210173@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin@cygwin.com \
--cc=evilworld015@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).