From: Stephen Leake <stephen_leake@stephe-leake.org>
To: emacs-devel <emacs-devel@gnu.org>
Subject: Re: gnutls on mingw64
Date: Wed, 27 Nov 2019 01:58:54 -0800 [thread overview]
Message-ID: <864kypprmp.fsf@stephe-leake.org> (raw)
In-Reply-To: <CAPM58ogS=oEv8d-PxZ3hxn=GVXNTssYFZ2FatTVftPGi__aGrg@mail.gmail.com> (Richard Copley's message of "Wed, 27 Nov 2019 08:56:38 +0000")
Richard Copley <rcopley@gmail.com> writes:
> On Wed, 27 Nov 2019 at 01:13, Stephen Leake <stephen_leake@stephe-leake.org>
> wrote:
>
>> Richard Copley <rcopley@gmail.com> writes:
>>
>> So the dependency list in mingw pacman is incorrect for libgnutls. I've
>> reported this via the mingw64 github issues page:
>> https://github.com/msys2/MINGW-packages/issues/5997
>>
>> Hmm. pacman has a package msys/libhogweed 3.5.1, which installs
>> d:/msys64/mingw64/bin/libhogweed-4.dll; wrong version. Sigh.
>>
> $ pacman -Ssq nettle
> mingw-w64-i686-nettle
> mingw-w64-x86_64-nettle
> libnettle
> libnettle-devel
> nettle
>
> It's the native package, mingw-w64-x86_64-nettle, that you want.
Sigh; I only searched for "libnettle", not "nettle".
Now gnutls-available-p is returning non-nil; thanks for your help.
--
-- Stephe
next prev parent reply other threads:[~2019-11-27 9:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-26 12:34 gnutls on mingw64 Stephen Leake
2019-11-26 15:42 ` Richard Copley
2019-11-27 1:10 ` Stephen Leake
2019-11-27 8:56 ` Richard Copley
2019-11-27 9:58 ` Stephen Leake [this message]
2019-11-26 15:46 ` Eli Zaretskii
2019-11-27 10:00 ` Stephen Leake
2019-11-27 15:53 ` Eli Zaretskii
2019-11-28 18:00 ` Stephen Leake
2019-11-28 22:22 ` Richard Copley
2019-11-29 7:17 ` Eli Zaretskii
2019-11-29 8:32 ` Richard Copley
2019-11-29 10:24 ` Eli Zaretskii
2019-11-29 3:16 ` Juanma Barranquero
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=864kypprmp.fsf@stephe-leake.org \
--to=stephen_leake@stephe-leake.org \
--cc=emacs-devel@gnu.org \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.