From: Thorsten Kukuk <kukuk@suse.de>
To: Mike Frysinger <vapier@gentoo.org>
Cc: libtirpc-devel@lists.sourceforge.net, linux-nfs@vger.kernel.org
Subject: Re: [Libtirpc-devel] [PATCH libtirpc] fix build w/gssapi disabled
Date: Thu, 7 May 2015 09:40:46 +0200 [thread overview]
Message-ID: <20150507074046.GA13973@suse.de> (raw)
In-Reply-To: <1430983149-22199-1-git-send-email-vapier@gentoo.org>
Hi,
On Thu, May 07, Mike Frysinger wrote:
> Starting with commit d5259e751111cb108c784b044296185f543fc0be (Add header
> definitions for rpc_gss_*() APIs), the gss headers were pulled in all the
> time leading to build failures like so:
> CC libtirpc_la-bindresvport.lo
> In file included from ../tirpc/rpc/svc_auth.h:44:0,
> from ../tirpc/rpc/rpc.h:68,
> from bindresvport.c:46:
> ../tirpc/rpc/rpcsec_gss.h:38:27: fatal error: gssapi/gssapi.h: No such file or directory
This will not work since this headers will be installed in
/usr/include and other appliations compiled against libtirpc
will never define HAVE_RPCSEC_GSS, thus never see this interfaces.
We need something like the glibc features.h file, which will always
be included and defines, how tirpc was configured.
Thorsten
> Signed-off-by: Mike Frysinger <vapier@gentoo.org>
> ---
> tirpc/rpc/svc_auth.h | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/tirpc/rpc/svc_auth.h b/tirpc/rpc/svc_auth.h
> index 44b38bf..998b13a 100644
> --- a/tirpc/rpc/svc_auth.h
> +++ b/tirpc/rpc/svc_auth.h
> @@ -41,6 +41,8 @@
> #ifndef _RPC_SVC_AUTH_H
> #define _RPC_SVC_AUTH_H
>
> +#ifdef HAVE_RPCSEC_GSS
> +
> #include <rpc/rpcsec_gss.h>
>
> typedef struct {
> @@ -51,6 +53,8 @@ typedef struct {
> u_int seq_num;
> } svc_rpc_gss_parms_t;
>
> +#endif
> +
> /*
> * Interface to server-side authentication flavors.
> */
> @@ -63,8 +67,10 @@ typedef struct SVCAUTH {
> int (*svc_ah_destroy)(struct SVCAUTH *);
> } *svc_ah_ops;
> caddr_t svc_ah_private;
> +#ifdef HAVE_RPCSEC_GSS
> svc_rpc_gss_parms_t svc_gss_params;
> rpc_gss_rawcred_t raw_cred;
> +#endif
> } SVCAUTH;
>
> #define SVCAUTH_WRAP(auth, xdrs, xfunc, xwhere) \
> --
> 2.4.0
>
>
> ------------------------------------------------------------------------------
> One dashboard for servers and applications across Physical-Virtual-Cloud
> Widest out-of-the-box monitoring support with 50+ applications
> Performance metrics, stats and reports that give you Actionable Insights
> Deep dive visibility with transaction tracing using APM Insight.
> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
> _______________________________________________
> Libtirpc-devel mailing list
> Libtirpc-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/libtirpc-devel
--
Thorsten Kukuk, Senior Architect SLES & Common Code Base
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany
GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg)
next prev parent reply other threads:[~2015-05-07 7:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-07 7:19 [PATCH libtirpc] fix build w/gssapi disabled Mike Frysinger
2015-05-07 7:40 ` Thorsten Kukuk [this message]
2015-05-07 8:23 ` [Libtirpc-devel] " Mike Frysinger
2015-05-07 8:51 ` Thorsten Kukuk
2015-05-07 11:52 ` Thorsten Kukuk
2015-05-07 15:12 ` Mike Frysinger
2015-05-07 15:24 ` Steve Dickson
2015-05-07 15:38 ` Steve Dickson
2015-05-07 16:33 ` Thorsten Kukuk
2015-05-07 16:55 ` Steve Dickson
2015-05-07 18:12 ` Thorsten Kukuk
2015-05-07 20:04 ` Steve Dickson
2015-05-07 20:12 ` Steve Dickson
2015-05-07 20:24 ` [PATCH V2] Fix Build " Steve Dickson
2015-05-08 2:03 ` Mike Frysinger
2015-05-08 8:17 ` Thorsten Kukuk
2015-05-08 21:27 ` Steve Dickson
2015-05-08 22:34 ` Thorsten Kukuk
2015-05-08 3:33 ` Steve Dickson
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=20150507074046.GA13973@suse.de \
--to=kukuk@suse.de \
--cc=libtirpc-devel@lists.sourceforge.net \
--cc=linux-nfs@vger.kernel.org \
--cc=vapier@gentoo.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.
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 NNTP newsgroup(s).