From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: Glenn Morris <rgm@gnu.org>
Cc: 19168@debbugs.gnu.org
Subject: bug#19168: undefined references to gnutls_pk_bits_to_sec_param etc
Date: Tue, 25 Nov 2014 18:24:28 +0100 [thread overview]
Message-ID: <m3zjbf5h2r.fsf@stories.gnus.org> (raw)
In-Reply-To: <kqwq6ji51l.fsf@fencepost.gnu.org> (Glenn Morris's message of "Tue, 25 Nov 2014 12:05:58 -0500")
Glenn Morris <rgm@gnu.org> writes:
> BTW, unrelated, but configure says this:
>
> checking for LIBGNUTLS... no
> checking for LIBGNUTLS... yes
>
> which is a bit unclear...
Yes. Is it the check for GNUTLS3 that fails, perhaps? My autoconf-foo
is in the negative region, so I'm not sure what should be changed here...
HAVE_GNUTLS=no
HAVE_GNUTLS3=no
if test "${with_gnutls}" = "yes" ; then
EMACS_CHECK_MODULES([LIBGNUTLS], [gnutls >= 3.0.0],
[HAVE_GNUTLS3=yes], [HAVE_GNUTLS3=no])
if test "${HAVE_GNUTLS3}" = "yes"; then
AC_DEFINE(HAVE_GNUTLS3, 1, [Define if using GnuTLS v3.])
HAVE_GNUTLS="yes"
else
EMACS_CHECK_MODULES([LIBGNUTLS], [gnutls >= 2.6.6],
[HAVE_GNUTLS=yes], [HAVE_GNUTLS=no])
fi
if test "${HAVE_GNUTLS}" = "yes"; then
AC_DEFINE(HAVE_GNUTLS, 1, [Define if using GnuTLS.])
fi
# Windows loads GnuTLS dynamically
if test "${opsys}" = "mingw32"; then
LIBGNUTLS_LIBS=
fi
fi
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2014-11-25 17:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-24 17:24 bug#19168: undefined references to gnutls_pk_bits_to_sec_param etc Glenn Morris
2014-11-24 17:33 ` Lars Magne Ingebrigtsen
2014-11-25 9:42 ` Ted Zlatanov
2014-11-25 14:48 ` Lars Magne Ingebrigtsen
2014-11-25 15:11 ` Ted Zlatanov
2014-11-25 15:05 ` Lars Magne Ingebrigtsen
2014-11-25 17:05 ` Glenn Morris
2014-11-25 17:24 ` Lars Magne Ingebrigtsen [this message]
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=m3zjbf5h2r.fsf@stories.gnus.org \
--to=larsi@gnus.org \
--cc=19168@debbugs.gnu.org \
--cc=rgm@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).