From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: mingw64-x86_64-libidn2 is out-of-date, causes linking fail
Date: Sat, 5 Feb 2022 14:57:19 -0700 [thread overview]
Message-ID: <aa4619dd-f97c-cb98-a6c8-ad12d3ca7368@SystematicSw.ab.ca> (raw)
In-Reply-To: <f5bmtj5w56i.fsf@ecclerig.inf.ed.ac.uk>
On 2022-02-05 11:15, Henry S. Thompson wrote:
> There's a version skew problem between the current gnutls (3.5.18)
> and libidn2 (2.3.2) in mingw64-x86_64. This tickles an old bug (see
> e.g. this bug report [1]) at runtime, namely:
> entry point "_idn2_punycode_decode" could not be found in
> .../libgnutls-30.dlls-30.dll
> Downgrading mingw64-x86_64-libidn2 from 2.3.2 (2021) to 2.0,4 (2017)
> fixes the problem, but may or may not introduce other issues down the
> line.
> Any chance we could get an update to the mingw64-x86_64-gnutls
> package? I note that the libgnutls30 package is at 3.6.9, and gnutls
> stable itself is at 3.6.16.
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1683812
It is currently ORPHANED so I had a look a year or so ago at getting
base Cygwin gnutls up to date for htmldoc, wget/2 but found ORPHANED
required dependency upgrades which had cygport build problems I couldn't
address.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]
prev parent reply other threads:[~2022-02-05 21:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-05 18:15 Henry S. Thompson
2022-02-05 21:57 ` Brian Inglis [this message]
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=aa4619dd-f97c-cb98-a6c8-ad12d3ca7368@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).