From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Couldn't compute FAST_CWD pointer
Date: Thu, 03 May 2018 18:24:00 -0000 [thread overview]
Message-ID: <2750cb81-854e-42b2-2462-bc6d1529db38@cygwin.com> (raw)
In-Reply-To: <d435cb4dbf9517c84d073132f3eac6bb@susu.inaoep.mx>
On 2018-05-03 13:20, emoctezuma wrote:
> Good afternoon, I am using a IC-CAP 2016.1Â Â and when i trying to
> simulate a simple circuit to get its S parameters
> the simulation send the next warning:
> 1 [main] cp 9736 find_fast_cwd: WARNING: Couldn't compute FAST_CWD
> pointer. Please report this problem to
> the public mailing list cygwin@cygwin.com
https://cygwin.com/faq/faq.html#faq.using.fixing-find_fast_cwd-warnings
--
Yaakov
--
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-05-03 18:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-03 18:20 emoctezuma
2018-05-03 18:24 ` Yaakov Selkowitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-08-19 12:11 Rick.Grape
2022-08-19 12:15 ` cygwinautoreply
2022-08-19 12:23 ` Oskar Skog
2022-08-21 15:28 ` Erik Soderquist
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
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=2750cb81-854e-42b2-2462-bc6d1529db38@cygwin.com \
--to=yselkowitz@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).