From: Juanma Barranquero <lekktu@gmail.com>
To: Ted Zlatanov <tzz@lifelogs.com>
Cc: nyc4bos@aol.com, 8825@debbugs.gnu.org
Subject: bug#8825: 24.0.50; Problem with builtin gnutls on Windows
Date: Sun, 19 Jun 2011 05:07:41 +0200 [thread overview]
Message-ID: <BANLkTimfa0NcJ9PwOCOsEChJtzu2WuU2aQ@mail.gmail.com> (raw)
In-Reply-To: <87r56qblpn.fsf@lifelogs.com>
2011/6/19 Ted Zlatanov <tzz@lifelogs.com>:
> I am 100% sure, however,
> that if `gnutls-boot' is a void function, this means that Emacs was
> compiled without HAVE_GNUTLS. That's what Juanma is saying too.
Yes, that's what's happening here. I compiled the trunk without GnuTLS
support and I get the exact same error as the OP:
Debugger entered--Lisp error: (void-function gnutls-boot)
gnutls-boot(#<process tls> gnutls-x509pki (:priority "NORMAL"
:hostname "imap.aim.com" :loglevel 0 :trustfiles nil :crlfiles nil
:keylist nil :verify-flags nil :verify-error nil
:verify-hostname-error nil :callbacks nil))
gnutls-negotiate(:process #<process tls> :type gnutls-x509pki
:hostname "imap.aim.com")
open-gnutls-stream("tls" "tls-buffer" "imap.aim.com" "imaps")
eval((open-gnutls-stream "tls" "tls-buffer" "imap.aim.com" "imaps") nil)
eval-last-sexp-1(nil)
eval-last-sexp(nil)
call-interactively(eval-last-sexp nil nil)
vs. the following error when the DLL is not found:
Debugger entered--Lisp error: (error "GnuTLS not available")
gnutls-boot(#<process tls> gnutls-x509pki (:priority "NORMAL"
:hostname "imap.aim.com" :loglevel 0 :trustfiles nil :crlfiles nil
:keylist nil :verify-flags nil :verify-error nil
:verify-hostname-error nil :callbacks nil))
gnutls-negotiate(:process #<process tls> :type gnutls-x509pki
:hostname "imap.aim.com")
open-gnutls-stream("tls" "tls-buffer" "imap.aim.com" "imaps")
eval((open-gnutls-stream "tls" "tls-buffer" "imap.aim.com" "imaps") nil)
eval-last-sexp-1(nil)
eval-last-sexp(nil)
call-interactively(eval-last-sexp nil nil)
Juanma
next prev parent reply other threads:[~2011-06-19 3:07 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-08 21:48 bug#8825: 24.0.50; Problem with builtin gnutls on Windows nyc4bos
2011-06-08 23:39 ` Juanma Barranquero
2011-06-09 7:38 ` Eli Zaretskii
2011-06-09 9:43 ` Juanma Barranquero
2011-06-10 20:37 ` Sean Sieger
2011-06-14 23:28 ` nyc4bos
2011-06-15 0:48 ` Juanma Barranquero
2011-06-15 15:19 ` Ted Zlatanov
2011-06-15 21:37 ` nyc4bos
2011-06-17 21:42 ` Sean Sieger
2011-06-17 22:00 ` Sean Sieger
2011-06-18 16:47 ` nyc4bos
2011-06-19 0:13 ` Juanma Barranquero
2011-06-19 2:26 ` Ted Zlatanov
2011-06-19 3:07 ` Juanma Barranquero [this message]
2011-06-19 10:59 ` Sean Sieger
2011-06-19 11:24 ` Juanma Barranquero
2011-06-19 11:25 ` Juanma Barranquero
2011-06-19 12:39 ` Sean Sieger
2011-06-19 14:56 ` Ted Zlatanov
2011-06-20 17:11 ` Sean Sieger
2011-06-20 20:10 ` Juanma Barranquero
2011-06-20 22:16 ` Sean Sieger
2011-06-20 22:48 ` Juanma Barranquero
2011-06-20 23:22 ` nyc4bos
2011-06-21 12:02 ` Ted Zlatanov
2011-06-11 1:17 ` Ted Zlatanov
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=BANLkTimfa0NcJ9PwOCOsEChJtzu2WuU2aQ@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=8825@debbugs.gnu.org \
--cc=nyc4bos@aol.com \
--cc=tzz@lifelogs.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).