public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Klaas Dieckhoff <klaas.dieckhoff@googlemail.com>
To: cygwin@cygwin.com
Subject: AW: Setup: gio-querymodules.exe - Entrypoint not found
Date: Fri, 18 Jun 2021 09:08:32 +0200	[thread overview]
Message-ID: <CACuu4WK22EXfRF8=M-qRCZVoHEiy6KPS9bXTrjg+7auxoc4u4A@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 3179 bytes --]

First of all sorry for sending this from another address, but my other one
seems to be blocked by the spam filter...

> > 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 attached a screenshot of the error message.

>

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



Okay, trying to download  a file with wget gives me a 'Scheme Missing'.

>

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



No, I downloaded and installed Cygwin last week, I did also check for
updates this morning. Actually there were some git related upates but this
didn't fix it.

>

> 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

>



I get the same output here then you did. Yes I had Git for windows
installed. But I removed this when trying to fix this on my own. It's maybe
worth mentioning, that git for windows also stopped being able to push
after I installed Cygwin. Before this worked and git is also still working
on my Linux VM. So I don't expect it to be some network problem.



Any other idea?



Thanks

Klaas

> --

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

>

> --

> Problem reports:      https://cygwin.com/problems.html

> FAQ:                  https://cygwin.com/faq/

> Documentation:        https://cygwin.com/docs.html

> Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple

>

[-- Attachment #2: error_cygwin_setup.png --]
[-- Type: image/png, Size: 9358 bytes --]

                 reply	other threads:[~2021-06-18  7:08 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='CACuu4WK22EXfRF8=M-qRCZVoHEiy6KPS9bXTrjg+7auxoc4u4A@mail.gmail.com' \
    --to=klaas.dieckhoff@googlemail.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).