public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Setup: gio-querymodules.exe - Entrypoint not found
Date: Wed, 16 Jun 2021 00:41:30 -0600	[thread overview]
Message-ID: <d7f2b22f-794b-dfec-7821-baccd8dcd6e2@SystematicSw.ab.ca> (raw)
In-Reply-To: <CACuu4WJP2RQV=FaUS2nMr6m9PwaWNbKfKyDdpGwD1bFF7Rht1A@mail.gmail.com>

On 2021-06-15 23:14, Klaas Dieckhoff via Cygwin wrote:
> While installing Cygwin on my Windows 10 machine I got the attached error
> message twice. Unfortunately it’s in german, but it translates to:
> procedure entrypoint "_idn2_punycode_decode" not found in DLL
> <path>/libgnutls-30.dll
> In my installation I’m for example not able to use git with ssl (i.e.
> commands like ‘git push origin master’). I already tried to reinstall
> libgnutls-30.dll which didn’t help.
> Any idea how to resolve this issue?

Your subject mentions setup and gio-querymodules; your body mentions 
idn2_punycode_decode, libgnutls30; plus git and git-push.

Please copy and paste the actual commands executed and error messages 
reported, including complete commands for each of the issues involved.
There are German speakers on the list who can clarify for those of us 
who may have issues decoding German tech language.

I would not expect punycode to be anything to do with libgnutls.

I would expect idn2_punycode_decode in cyg/libidn2, but it is not a 
public API symbol for either Cygwin or Windows mingw libraries.

The idn2_punycode_decode issue was a libgnutls/libidn2 compatibility 
problem a couple of years ago but should be fixed now:

	https://bugzilla.redhat.com/show_bug.cgi?id=1683812

Cygwin wget and wget2 are built with libgnutls and libidn2 and have no 
build, test, or usage issues reported.

Have you perhaps an old release of Cygwin installed and have not applied 
any recent upgrades?

Do you perhaps have Git for Windows or some WSL distro installed and in 
your path? Try:

	$ which git; ls /usr/libexec/git-core/git-push
	/usr/bin/git
	/usr/libexec/git-core/git-push

-- 
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.]

  reply	other threads:[~2021-06-16  6:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-16  5:14 Klaas Dieckhoff
2021-06-16  6:41 ` Brian Inglis [this message]
2021-06-18 13:30   ` Ken Brown
2021-06-16  6:48 ` Marco Atzeri
2021-06-22 11:34 Klaas Dieckhoff

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=d7f2b22f-794b-dfec-7821-baccd8dcd6e2@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).