From: Jon Turney <jon.turney@dronecode.org.uk>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: setup 2.906 release candidate - please test
Date: Wed, 17 Mar 2021 20:08:06 +0000 [thread overview]
Message-ID: <b1e7d223-fc9a-4692-5730-f9e026e13a58@dronecode.org.uk> (raw)
In-Reply-To: <0d8d39fd-0bf0-225a-6963-1fa94a2f5037@dronecode.org.uk>
On 17/03/2021 20:02, Jon Turney wrote:
>
> A new setup release candidate is available at:
>
> https://cygwin.com/setup/setup-2.906.x86_64.exe (64 bit version)
> https://cygwin.com/setup/setup-2.906.x86.exe (32 bit version)
>
> Please test, and report any problems here.
>
> This is not the place for setup feature requests.
Pretty late in preparing this release, I discovered that in Fedora 33,
the MinGW-w64 32-bit compiler has been changed from sjlj to dwarf2
unwinding C++ exception handling.
I believe this means that exceptions cannot propagate up through Windows
code, so the release needs to be delayed until the source code has been
inspected to see if there's any place where e.g. we throw an exception
from a Windows callback, but I'd like to get this out for some testing
already.
next prev parent reply other threads:[~2021-03-17 20:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-17 20:02 Jon Turney
2021-03-17 20:08 ` Jon Turney [this message]
2021-04-26 12:00 ` Jon Turney
2021-03-17 21:16 ` Thomas Wolff
2021-03-17 21:29 ` Ken Brown
2021-03-21 0:33 ` Brian Inglis
[not found] <822157107.1286425.1616430946694.JavaMail.administrator@n5.nabble.com>
2021-03-25 19:11 ` Jon Turney
[not found] <182029171.1352421.1616703758747.JavaMail.administrator@n5.nabble.com>
2021-04-01 15:53 ` Jon Turney
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=b1e7d223-fc9a-4692-5730-f9e026e13a58@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin-apps@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).