From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-announce@cygwin.com
Subject: cygwin 3.4.1-1
Date: Sat, 10 Dec 2022 21:26:35 +0100 [thread overview]
Message-ID: <20221210212635.3195169-1-corinna-cygwin@cygwin.com> (raw)
The following packages have been uploaded to the Cygwin distribution:
* cygwin-3.4.1-1
* cygwin-devel-3.4.1-1
* cygwin-doc-3.4.1-1
This is a bugfix release.
- Fix a backward incompatibility problem in the definition of the
base type of the stdio type FILE. This requires that C++ binaries
compiled under Cygwin 3.4.0 having a public facing interface using
FILE need to be recompiled.
Addresses: https://savannah.gnu.org/bugs/index.php?63480
- Fix an error introduced into the build process, resulting in `gcc -pg'
becoming disfunctional.
Addresses: https://cygwin.com/pipermail/cygwin/2022-December/252619.html
- Fix performance degradation of non-cygwin pipe.
Addresses: https://cygwin.com/pipermail/cygwin/2022-December/252628.html
==========================================================================
IMPORTANT DEPRECATION NOTES
==========================================================================
- Cygwin 3.4 is the FIRST major version dropping support for
- 32 bit Windows including WOW64 on 64 bit Windows.
- Windows Vista
- Windows Server 2008
- Cygwin 3.4 is the LAST major version supporting
- Windows 7
- Windows Server 2008 R2
- Windows 8
- Windows Server 2012
- Cygwin 3.5, which will probably be release at some point in late 2023,
will run on
- Windows 8.1
- Windows 10
- Windows 11
- Windows Server 2012 R2
- Windows Server 2016
- Windows Server 2019
- Windows Server 2022
There are no plans to deprecate support for 64 bit systems starting with
Windows 8.1 / Windows Server 2012 R2 any time soon.
reply other threads:[~2022-12-10 20:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20221210212635.3195169-1-corinna-cygwin@cygwin.com \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin-announce@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).