From: Allen Hewes <allen@decisiv.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: [ANNOUNCEMENT] cygwin 3.3.4-1
Date: Mon, 31 Jan 2022 18:49:01 +0000 [thread overview]
Message-ID: <MN2PR17MB3999D5046A9A36970CB05121B8259@MN2PR17MB3999.namprd17.prod.outlook.com> (raw)
In-Reply-To: <d4dca0c8-a731-e3cd-de5a-f101cbf65da4@acm.org>
> From: Cygwin <cygwin-bounces+allen=decisiv.net@cygwin.com> On Behalf
> Of David Rothenberger
> Sent: Monday, January 31, 2022 1:39 PM
> To: cygwin@cygwin.com
> Subject: Re: [ANNOUNCEMENT] cygwin 3.3.4-1
>
> On 1/31/2022 10:34 AM, Jim Reisert AD1C wrote:
> >> The following packages have been uploaded to the Cygwin distribution:
> >>
> >> * cygwin-3.3.4-1
> >> * cygwin-devel-3.3.4-1
> >> * cygwin-doc-3.3.4-1
> >
> > I've tried two mirrors, both with the same result:
> >
> > dash.exe - Bad Image
> >
> > C:\Cygwin64\bin\cygwin1.dll is either not designed to run on
> > Windows or it contains an error....Error status 0xc000007b.
> >
> > I'm running Windows 11 Pro (21H2), OS Build 22000.469
> >
> > The previous version has been working just fine.
>
> I saw the same errors this morning with Windows 10 Pro for Workstations
> (10.0.19044). I also tried two mirrors. I ended up rolling back to the previous
> version as well.
Same here. There's something amiss with 3.3.4-1, IMHO. I grabbed the XZ's manually from mirrors.dotsrc.org.
Windows 10 Pro
Microsoft Windows [Version 10.0.19044.1503]
Working Cygwin:
CYGWIN_NT-10.0-19044 FOUREYES 3.3.3-341.x86_64 2021-12-03 16:35 UTC x86_64 Cygwin
/allen
________________________________
Disclaimer Confidentiality Notice: This e-mail, and any attachments and/or documents linked to this email, are intended for the addressee and may contain information that is privileged, confidential, proprietary, or otherwise protected by law. Any dissemination, distribution, or copying is prohibited. This notice serves as a confidentiality marking for the purpose of any confidentiality or nondisclosure agreement. If you have received this communication in error, please contact the original sender.
next prev parent reply other threads:[~2022-01-31 18:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-31 12:04 Corinna Vinschen via Cygwin-announce
2022-01-31 18:34 ` Jim Reisert AD1C
2022-01-31 18:38 ` David Rothenberger
2022-01-31 18:49 ` Allen Hewes [this message]
2022-01-31 22:20 ` Adam Dinwoodie
2022-02-01 0:03 ` David Schuler
2022-02-01 0:23 ` Allen Hewes
2022-02-01 17:02 ` Jim Reisert AD1C
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=MN2PR17MB3999D5046A9A36970CB05121B8259@MN2PR17MB3999.namprd17.prod.outlook.com \
--to=allen@decisiv.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).