From: Robert Pluim <rpluim@gmail.com>
To: Kaushal Modi <kaushal.modi@gmail.com>
Cc: Jude DaShiell <jdashiel@panix.com>,
Help Gnu Emacs mailing list <help-gnu-emacs@gnu.org>
Subject: Re: Special configuration needed for eww + gnutls? [emacs 28.1]
Date: Sun, 17 Apr 2022 16:14:43 +0200 [thread overview]
Message-ID: <878rs33igc.fsf@gmail.com> (raw)
In-Reply-To: <CAFyQvY2avvBcXG4+cH8CR+2S1QYO3VKzSkEYHVY83OiKvpySZw@mail.gmail.com> (Kaushal Modi's message of "Fri, 15 Apr 2022 14:00:01 -0400")
>>>>> On Fri, 15 Apr 2022 14:00:01 -0400, Kaushal Modi <kaushal.modi@gmail.com> said:
Kaushal> I tried updating gnutls locally on my machine (where I don't have root
Kaushal> privileges)
Kaushal> - Tried to update gnutls, but it failed because I don't have libnettle.
Kaushal> - Tried to install libnettle, but if failed because
Kaushal> "downloads/nettle-3.7.3/examples/nettle-openssl.c:408: undefined
Kaushal> reference to `EVP_MD_CTX_new'"
Kaushal> I guess I will have to ask the sysadmin to update the gnutls lib.
Kaushal> Thanks for your help! This explains why eww works for me the last time
Kaushal> it worked (> 2 years back) and why it doesn't work now.
I guess if you really,really want to use eww on that machine, you
could install gnutls-cli in your home directory somewhere, and
persuade emacs to use it instead of the built-in support (either by
explicitly disabling gnutls when configuring or by overriding
`gnutls-available-p'). Donʼt use the resulting emacs for anything
important, though 🙂
Robert
--
prev parent reply other threads:[~2022-04-17 14:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-14 16:34 Special configuration needed for eww + gnutls? [emacs 28.1] Kaushal Modi
2022-04-15 2:04 ` Jude DaShiell
2022-04-15 16:53 ` Kaushal Modi
2022-04-15 17:28 ` Robert Pluim
2022-04-15 18:00 ` Kaushal Modi
2022-04-17 14:14 ` Robert Pluim [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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878rs33igc.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=jdashiel@panix.com \
--cc=kaushal.modi@gmail.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).