unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: proposal: require GnuTLS 3.1.x (previous stable) (was: Build failure (master; MS-Windows))
Date: Tue, 25 Nov 2014 04:32:24 -0500	[thread overview]
Message-ID: <87389762xj.fsf_-_@lifelogs.com> (raw)
In-Reply-To: CAH8Pv0g3wkayJk-=KwYaM+AGt5ys1ss3ymf-bOY9TxK7d13ugg@mail.gmail.com

On Mon, 24 Nov 2014 00:09:40 +0100 Dani Moncayo <dmoncayo@gmail.com> wrote: 

>>> Now I the bootstrap ends without errors, but I still see these warnings:
>>> 
>>> c:/cygwin64/home/Dani/devel/emacs/repo/src/gnutls.c:130:1: warning:
>>> 'gnutls_connection_end_t' is deprecated [-Wdeprecated-declarations]
>> 
>> That line has been unchanged there for quite a while, I think.  The
>> definition here is the same as it is in gnutls 2.12.

DM> Ok, I've now realized that I updated my GnuTLS library on 2014-11-10,
DM> from version 3.0.9 to 3.3.9:

DM>   ftp://ftp.gnutls.org/gcrypt/gnutls/w32/gnutls-3.3.9-w32.zip

DM> I guess that explains the warning.

Maintainers: we're now targeting Emacs 25 in the master branch and 3.3.x
is the "next stable" version of GnuTLS. I think we should require GnuTLS
3.1.x ("previous stable") instead of 2.6.6 as we do now. In the C
source, that would make HAVE_GNUTLS3 always true, and we'll also may add
HAVE_GNUTLS3_2 and HAVE_GNUTLS3_3 (or special macros for each feature we
need).

Conditionally supporting GnuTLS 2.6.6 is a pain because many functions
were added since then. It complicates the code significantly today and
for the future, possibly hiding bugs in the compatibility layers. We're
already starting to see these compilation issues in the bug tracker and
on emacs-devel and it would be nice to cut the cord now.

Ted




  reply	other threads:[~2014-11-25  9:32 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-23 18:38 Build failure (master; MS-Windows) Dani Moncayo
2014-11-23 21:41 ` Dani Moncayo
2014-11-23 22:07   ` Lars Magne Ingebrigtsen
2014-11-23 22:52     ` Dani Moncayo
2014-11-23 22:57       ` Lars Magne Ingebrigtsen
2014-11-23 23:09         ` Dani Moncayo
2014-11-25  9:32           ` Ted Zlatanov [this message]
2014-11-25 15:57             ` proposal: require GnuTLS 3.1.x (previous stable) Lars Magne Ingebrigtsen
2014-11-25 16:28               ` Ted Zlatanov
2014-11-25 16:38                 ` Buildbot for Emacs? (was: proposal: require GnuTLS 3.1.x (previous stable)) Lars Magne Ingebrigtsen
2014-11-25 16:50                   ` Buildbot for Emacs? Glenn Morris
2014-11-25 16:55                     ` Ted Zlatanov
2014-11-25 22:15                       ` Glenn Morris
2014-11-25 23:12                         ` Ted Zlatanov
2014-11-26  9:52                         ` Tom
2014-11-25 17:05                     ` Lars Magne Ingebrigtsen
2014-11-25 22:14                       ` Glenn Morris
2014-11-25 17:34                 ` proposal: require GnuTLS 3.1.x (previous stable) Stefan Monnier
2014-11-25 18:55               ` Ivan Shmakov
2014-11-26  9:14                 ` Peder O. Klingenberg
2014-11-26 12:57                   ` Ivan Shmakov
2014-11-26 13:47                     ` Peder O. Klingenberg
2014-11-26 13:08                   ` Ted Zlatanov
2014-11-26 14:12                     ` Peder O. Klingenberg
2014-11-26 15:42                     ` Stefan Monnier
2014-11-26 16:52                       ` Ted Zlatanov
2014-11-26 21:18                         ` Ted Zlatanov
2014-11-26 21:37                           ` Lars Magne Ingebrigtsen
2014-11-27  2:13                           ` Stefan Monnier
2014-11-27  2:33                             ` Ted Zlatanov
2014-11-28 18:51                             ` Ted Zlatanov
2014-11-28 19:31                               ` Stefan Monnier
2014-11-29 20:02                               ` Glenn Morris
2014-11-26 13:46                   ` Michael Welsh Duggan

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=87389762xj.fsf_-_@lifelogs.com \
    --to=tzz@lifelogs.com \
    --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 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).