From: Steve Dickson <SteveD@redhat.com>
To: Thorsten Kukuk <kukuk@suse.de>, 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, 07 May 2015 11:38:10 -0400 [thread overview]
Message-ID: <554B86E2.8090908@RedHat.com> (raw)
In-Reply-To: <20150507115248.GA20243@suse.de>
Hello,
Boy I had no idea --disable-gssapi was so prevalent...
My apologies for breaking it...
On 05/07/2015 07:52 AM, Thorsten Kukuk wrote:
>
> 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
>
> Here is my proof of concept how I think we should solve this.
> But there is one part of your patch I have no solution for:
>
>> --- a/tirpc/rpc/svc_auth.h
>> +++ b/tirpc/rpc/svc_auth.h
> [...]
>> @@ -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;
>
> You are changeing the size of a struct here. I'm not sure
> if this will work, if an application is compiled with headers
> where it is disabled and then runs with a tirpc where it is
> enabled. Or the other way around.
> Does somebody have an idea how to solve that?
Maybe some type of place holders?? Since the gssapi
is on by default, they would be knowing breaking it,
if that matters...
>
> Else here is my patch:
Is this patch addition to Mike's patch?
steved.
next prev parent reply other threads:[~2015-05-07 15:38 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 ` [Libtirpc-devel] " Thorsten Kukuk
2015-05-07 8:23 ` 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 [this message]
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=554B86E2.8090908@RedHat.com \
--to=steved@redhat.com \
--cc=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).