From: Karl-Johan Karlsson <creideiki+linux-nfs@lysator.liu.se>
To: linux-nfs@vger.kernel.org, Steve Dickson <steved@redhat.com>
Subject: libtirpc-0.3.1 fails to build with Heimdal Kerberos
Date: Fri, 05 Jun 2015 14:18:33 +0200 [thread overview]
Message-ID: <2431059.CVRe3y6Cse@orley> (raw)
Hi,
I'm trying to debug a build failure for libtirpc-0.3.1 with GSSAPI support
when using Heimdal 1.5.3 as Kerberos provider. Downstream bug report is at
https://bugs.gentoo.org/show_bug.cgi?id=551036
src/svc_auth_gss.c has an unconditional
#include <gssapi/gssapi_ext.h>
but Heimdal doesn't ship that file; MIT-Krb5 does, though. It looks like most
(but not all) of the functions that MIT-Krb5 declares in <gssapi/gssapi_ext.h>
are declared in Heimdal by <gssapi/gssapi.h>.
src/svc_auth_gss.c has
#ifdef HAVE_KRB5
and
#elif HAVE_HEIMDAL
sections, but nothing I can see in the Autoconf system defines those.
configure.ac does have
AC_CHECK_HEADER([gssapi/gssapi.h], [HAVE_GSSAPI_H=yes], [HAVE_GSSAPI_H=no])
but that's just used internally in the configure script.
Would it be correct to export HAVE_GSSAPI_H and HAVE_GSSAPI_EXT_H to config.h
and have src/svc_auth_gss.c include gssapi.h and/or gssapi_ext.h depending on
them?
By the way, the link to the libtirpc gitweb on http://linux-nfs.org/wiki/index.php/Main_Page is broken. It points to http://git.linux-nfs.org/?p=steved/libtirpc.git;a=summary which is a 404.
--
Karl-Johan Karlsson
next reply other threads:[~2015-06-05 12:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-05 12:18 Karl-Johan Karlsson [this message]
2015-06-05 14:17 ` libtirpc-0.3.1 fails to build with Heimdal Kerberos Chuck Lever
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=2431059.CVRe3y6Cse@orley \
--to=creideiki+linux-nfs@lysator.liu.se \
--cc=linux-nfs@vger.kernel.org \
--cc=steved@redhat.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.
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.