unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: hi@yagnesh.org, 19346@debbugs.gnu.org, larsi@gnus.org
Subject: bug#19346: 25.0.50; url-http-parse-headers: Symbol's function definition is void:	gnutls-available-p
Date: Thu, 11 Dec 2014 17:58:36 -0500	[thread overview]
Message-ID: <878uid4wv7.fsf@lifelogs.com> (raw)
In-Reply-To: <83ppbpsxtu.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 11 Dec 2014 23:03:57 +0200")

On Thu, 11 Dec 2014 23:03:57 +0200 Eli Zaretskii <eliz@gnu.org> wrote: 

EZ> In gnutls.c, of course.

All right, fixed in emacs-24 and can be merged forward to master:

commit 301a4014a72964a8ec0078055c273d045d94fe42
Author: Ted Zlatanov <tzz@lifelogs.com>
Date:   Thu Dec 11 17:55:36 2014 -0500

    Always define `gnutls-available-p' even if GnuTLS is not available.
    
    Fixes: debbugs:19346
    
    * gnutls.c (Fgnutls_available_p syms_of_gnutls): Move later for
    clarity.  Let the availability check return Qnil when the GnuTLS
    integration is not available, instead of erroring out.
    
    * gnutls.h: Always declare syms_of_gnutls.
    
    * emacs.c (main): Always include gnutls.h and run syms_of_gnutls.

Lars, you can revert your patch if you want, after this is merged in.

EZ> The generic solution is for the code that links to each module to
EZ> provide the function, and for the module to provide the value.

EZ> This is all part of the "protocol" between Emacs and the modules,
EZ> which includes a header file, an import library, and a bunch of
EZ> interfaces each module needs to implement.

OK. I'll keep this in mind for when we get to that point.  It makes a
lot of sense.

Thanks
Ted





  reply	other threads:[~2014-12-11 22:58 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-11 10:57 bug#19346: 25.0.50; url-http-parse-headers: Symbol's function definition is void: gnutls-available-p Yagnesh Raghava Yakkala
2014-12-11 15:57 ` Lars Magne Ingebrigtsen
2014-12-11 16:08   ` Ted Zlatanov
2014-12-11 16:16     ` Lars Magne Ingebrigtsen
2014-12-11 18:00     ` Eli Zaretskii
2014-12-11 19:16       ` Stefan Monnier
2014-12-11 19:48       ` Ted Zlatanov
2014-12-11 21:03         ` Eli Zaretskii
2014-12-11 22:58           ` Ted Zlatanov [this message]
2014-12-12  0:02           ` Stefan Monnier
2014-12-12  0:21             ` Ted Zlatanov
2014-12-12  1:33               ` Stefan Monnier
2014-12-12  7:58                 ` Eli Zaretskii
2014-12-12 14:40                   ` Stefan Monnier
2014-12-12 14:54                     ` Eli Zaretskii
2014-12-12 16:39                       ` Stefan Monnier
2014-12-12 19:04                         ` Eli Zaretskii
2014-12-12 21:56                           ` Stefan Monnier
2014-12-13  7:43                             ` Eli Zaretskii
2014-12-13 14:21                               ` Stefan Monnier
2014-12-13 15:20                                 ` Eli Zaretskii
2014-12-12 13:19                 ` Ted Zlatanov
2014-12-12 14:47                   ` Stefan Monnier
2014-12-12  7:49             ` Eli Zaretskii
2014-12-12 14:42               ` Stefan Monnier
2014-12-12 14:55                 ` Eli Zaretskii
2014-12-12 16:33                   ` Stefan Monnier

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=878uid4wv7.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=19346@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=hi@yagnesh.org \
    --cc=larsi@gnus.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).