From: Eli Zaretskii <eliz@gnu.org>
To: Alexander Shukaev <haroogan@gmail.com>
Cc: andrewjmoreton@gmail.com, emacs-devel@gnu.org
Subject: Re: Updated GnuTLS from MSYS2 and Emacs's `dynamic-library-alist'
Date: Thu, 30 Apr 2015 18:47:55 +0300 [thread overview]
Message-ID: <83sibhsjmc.fsf@gnu.org> (raw)
In-Reply-To: <CAKu-7WwqTZKY0As8hUqM9jXBD2cXj=rc_KT95NY9YBbF8Uvy1Q@mail.gmail.com>
> Date: Thu, 30 Apr 2015 17:06:51 +0200
> From: Alexander Shukaev <haroogan@gmail.com>
> Cc: Andy Moreton <andrewjmoreton@gmail.com>, emacs-devel <emacs-devel@gnu.org>
>
> As I understand it
>
> (gnutls
> "libgnutls-
> 30
> .dll" "libgnutls-28.dll" "libgnutls-26.dll")
>
> makes loading of GnuTLS 3.4 completely optional, i.e. people may still have
> "libgnutls-28.dll" and use it instead. So why not backport this commit then?
That's not what needs to be done. Emacs compiled for GnuTLS versions
before 3.4.0 is incompatible with the GnuTLS DLL versions 3.4.0. The
new ABI introduces a binary incompatibility, so you need to recompile
Emacs with the newer GnuTLS headers to be able to load the 3.4.0 DLL.
And if you recompile Emacs like that, it will be incompatible with the
older DLLs. Trying to load incompatible DLLs will likely cause a
crash.
So the change you need to do is more than just the one you show.
Once again, I don't recommend that, if you are building a binary for
more than just your own consumption. But that's up to you.
next prev parent reply other threads:[~2015-04-30 15:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-30 11:46 Updated GnuTLS from MSYS2 and Emacs's `dynamic-library-alist' Alexander Shukaev
2015-04-30 13:43 ` Andy Moreton
2015-04-30 14:17 ` Eli Zaretskii
2015-04-30 15:06 ` Alexander Shukaev
2015-04-30 15:47 ` Eli Zaretskii [this message]
2015-04-30 16:05 ` Alexander Shukaev
2015-04-30 16:20 ` Eli Zaretskii
2015-04-30 14:09 ` Eli Zaretskii
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=83sibhsjmc.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=andrewjmoreton@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=haroogan@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.
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).