From: Lars Ingebrigtsen <larsi@gnus.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Eli Zaretskii <eliz@gnu.org>,
Dmitry Antipov <dmantipov@yandex.ru>,
emacs-devel@gnu.org
Subject: Re: --enable-gcc-warnings is broken on Fedora 21 by GnuTLS code
Date: Fri, 26 Dec 2014 01:25:11 +0100 [thread overview]
Message-ID: <871tnn5kbc.fsf@building.gnus.org> (raw)
In-Reply-To: <549CA974.5000807@cs.ucla.edu> (Paul Eggert's message of "Thu, 25 Dec 2014 16:19:00 -0800")
Paul Eggert <eggert@cs.ucla.edu> writes:
> Proposed patches attached. The first patch
> is purely a mechanical one to simplify maintenance, so that the
> mainline part of src/gnutls.c can use ordinary identifiers like
> gnutls_global_init instead of funky names like like
> fn_gnutls_global_init (the patch moves the funky names into the
> WINDOWSNT section).
Thanks; that's a great improvement.
> The second patch fixes src/gnutls.c to check for
> memory exhaustion after every call to a GnuTLS function that can
> report memory exhaustion, instead of relying on the deprecated
> gnutls_global_set_mem_functions API.
Looks good to me.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
next prev parent reply other threads:[~2014-12-26 0:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-12 8:38 --enable-gcc-warnings is broken on Fedora 21 by GnuTLS code Dmitry Antipov
2014-12-12 9:07 ` Eli Zaretskii
2014-12-12 9:26 ` Paul Eggert
2014-12-23 10:52 ` Dmitry Antipov
2014-12-23 18:28 ` Eli Zaretskii
2014-12-23 21:26 ` Paul Eggert
2014-12-24 7:07 ` Dmitry Antipov
2014-12-26 0:19 ` Paul Eggert
2014-12-26 0:25 ` Lars Ingebrigtsen [this message]
2014-12-26 8:23 ` Eli Zaretskii
2014-12-26 17:38 ` Paul Eggert
2014-12-27 8:08 ` Eli Zaretskii
2014-12-28 8:38 ` Paul Eggert
2014-12-28 15:20 ` Eli Zaretskii
2014-12-12 9:09 ` Paul Eggert
2014-12-12 9:30 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871tnn5kbc.fsf@building.gnus.org \
--to=larsi@gnus.org \
--cc=dmantipov@yandex.ru \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.