From: Ted Zlatanov <tzz@lifelogs.com>
To: 10612@debbugs.gnu.org
Cc: help-emacs-windows@gnu.org, emacs-devel@gnu.org
Subject: bug#10612: GnuTLS bundled with the windows Emacs binaries (was: bug#10215: 24.0.92; Can't contact nnimap (gnutls-cli not found))
Date: Thu, 26 Jan 2012 09:44:03 -0600 [thread overview]
Message-ID: <87wr8e8o58.fsf_-_@lifelogs.com> (raw)
In-Reply-To: 87ipjzs512.fsf@gnus.org
On Thu, 26 Jan 2012 01:04:25 +0100 Lars Ingebrigtsen <larsi@gnus.org> wrote:
LI> Uwe Siart <uwe.siart@tum.de> writes:
>> Thanks a lot for pointing me to that and sorry for my stupidness. I
>> wasn't aware that additional software is necessary because it hasn't
>> been necessary for Emacs 23.3 (precompiled for Windows). More even I
>> wasn't aware that GnuTLS is available for Windows.
LI> Hopefully Emacs 24 will be distributed (for Windows) with the GnuTLS
LI> libraries included, so that this will just work out of the box.
LI> Otherwise I think there will be many similar bug reports. :-)
Christoph has been doing that, I think, so we can rely on his binaries.
Christoph, can you add a GnuTLS build step to your Emacs build for
Windows, so the latest GnuTLS version can be used on that platform? We
had a long conversation about this and at least for now it seems to be
the best approach (and we agreed it would not be a task for the core
Emacs developers). If you prefer, I can set up a BuildBot to produce
the GnuTLS DLLs for you.
Ted
next parent reply other threads:[~2012-01-26 15:44 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <84boromyob.fsf@tum.de>
[not found] ` <m3lipk5scv.fsf@stories.gnus.org>
[not found] ` <84ipknew07.fsf@tum.de>
[not found] ` <87ipjzs512.fsf@gnus.org>
2012-01-26 15:44 ` Ted Zlatanov [this message]
2012-01-26 15:15 ` bug#10612: GnuTLS bundled with the windows Emacs binaries (was: bug#10215: 24.0.92; Can't contact nnimap (gnutls-cli not found)) Juanma Barranquero
2012-01-26 19:32 ` bug#10612: GnuTLS bundled with the windows Emacs binaries Ted Zlatanov
2012-01-26 19:36 ` [h-e-w] " Eli Zaretskii
2012-01-26 21:07 ` Ted Zlatanov
2012-01-26 21:39 ` Eli Zaretskii
2012-01-27 15:59 ` Ted Zlatanov
2012-01-27 15:30 ` Juanma Barranquero
2012-01-30 12:59 ` Ted Zlatanov
2012-01-27 15:45 ` Eli Zaretskii
2012-01-26 22:53 ` Juanma Barranquero
2012-03-17 15:41 ` Uday S Reddy
2012-03-17 18:11 ` Eli Zaretskii
2012-03-22 18:38 ` Lars Magne Ingebrigtsen
2014-12-08 20:05 ` Lars Magne Ingebrigtsen
2014-12-08 20:31 ` Drew Adams
2014-12-08 20:50 ` Eli Zaretskii
2014-12-08 20:56 ` Lars Magne Ingebrigtsen
2014-12-08 21:10 ` Óscar Fuentes
2014-12-08 21:24 ` Lars Magne Ingebrigtsen
2016-02-05 7:28 ` Lars Ingebrigtsen
2012-01-29 16:00 ` Christoph Scholtes
2012-01-29 16:47 ` Juanma Barranquero
2012-01-29 17:08 ` Christoph Scholtes
2012-01-29 17:26 ` Juanma Barranquero
2012-01-30 1:00 ` Chong Yidong
2012-01-30 12:53 ` Ted Zlatanov
2012-01-29 17:05 ` Eli Zaretskii
2012-01-30 13:07 ` Ted Zlatanov
2012-01-30 13:18 ` 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
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=87wr8e8o58.fsf_-_@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=10612@debbugs.gnu.org \
--cc=bug-gnu-emacs@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=help-emacs-windows@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 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).