From: "Jerry Baker via cygwin" <cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Cygwin 3.0.1-1 Breaks ALL cygwin applications on Windows 7 x64
Date: Wed, 27 Feb 2019 00:50:00 -0000 [thread overview]
Message-ID: <35062835-c3cd-799e-d13a-16f954db2a19@yahoo.com> (raw)
In-Reply-To: <CAJ1FpuO1nVEySyK1rc7c4AGx4+GsAHikBb54akebky8-yXM1HQ@mail.gmail.com>
On 2/26/2019 2:48 PM, Doug Henderson wrote:
> Good. This tells us something important. Right after the path listing,
> cygcheck list "Output from C:\cygwin64\bin\id.exe". The id exe is a
> cygwin exe which uses cygwin1.dll, cygintl-8.dll, and cygiconv-2.dll.
>
> That narrow the problem. These three DLLs might have been corrupted,
> or something is interfering with their correct operation.
>
> See BLODA: See https://cygwin.com/acronyms/
>
> Check the list of BLODAs to see if you are running one of those.
It's just cygwin1.dll for sure. I can replace that with 2.x version and
everything works fine.
I don't recognize most of the BLODAs and not running any of them that I
know of. Are there any software packages known to interfere with 3.0 and
not 2.x?
--
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:[~2019-02-26 23:00 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-26 16:28 Jerry Baker via cygwin
2019-02-26 18:30 ` Jerry Baker via cygwin
2019-02-26 18:38 ` Houder
2019-02-26 18:44 ` Jerry Baker via cygwin
2019-02-26 18:45 ` Richard Campbell
2019-02-26 18:59 ` Vince Rice
2019-02-26 19:19 ` Jerry Baker via cygwin
2019-02-26 19:32 ` Ken Brown
2019-02-26 20:00 ` Jerry Baker via cygwin
2019-02-26 20:42 ` Jerry Baker via cygwin
2019-02-26 21:09 ` Vince Rice
2019-02-26 22:10 ` Doug Henderson
2019-02-26 22:19 ` Jerry Baker via cygwin
2019-02-26 22:48 ` Jerry Baker via cygwin
2019-02-26 23:00 ` Doug Henderson
2019-02-27 0:50 ` Jerry Baker via cygwin [this message]
2019-02-27 1:50 ` Steven Penny
2019-02-27 2:01 ` Jerry Baker via cygwin
2019-02-27 2:43 ` Jerry Baker via cygwin
2019-02-27 3:21 ` Doug Henderson
2019-02-27 3:45 ` Jerry Baker via cygwin
2019-02-27 6:55 ` Houder
2019-02-27 2:56 ` Steven Penny
2019-02-27 3:05 ` Jerry Baker via cygwin
2019-02-27 3:12 ` Steven Penny
2019-02-27 3:27 ` Jerry Baker via cygwin
2019-02-27 5:11 ` Steven Penny
2019-02-27 16:17 ` E. Madison Bray
2019-02-27 5:57 ` Vince Rice
2019-02-27 7:26 ` Brian Inglis
2019-02-27 20:23 ` Jerry Baker via cygwin
2019-02-27 20:27 ` Jerry Baker via cygwin
2019-02-27 20:50 ` Jerry Baker via cygwin
2019-02-27 21:48 ` Corinna Vinschen
2019-02-28 3:12 ` Jerry Baker via cygwin
2019-02-28 9:39 ` L A Walsh
2019-02-28 10:52 ` Corinna Vinschen
2019-03-11 21:27 ` Bill Stewart
2019-03-11 21:38 ` Achim Gratz
2019-03-11 21:46 ` Bill Stewart
2019-03-12 0:20 ` Andrey Repin
2019-02-27 20:44 ` Eric Blake
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=35062835-c3cd-799e-d13a-16f954db2a19@yahoo.com \
--to=cygwin@cygwin.com \
--cc=jbaker6953@yahoo.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).