From: Thorsten Kukuk <kukuk@suse.de>
To: 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 10:51:00 +0200 [thread overview]
Message-ID: <20150507085100.GA17102@suse.de> (raw)
In-Reply-To: <20150507082344.GD30924@vapier>
On Thu, May 07, Mike Frysinger wrote:
> On 07 May 2015 09:40, Thorsten Kukuk wrote:
> > 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.
>
> this is what tirpc/rpc/rpc.h is already doing ...
Ok, I haven't seen that this is already broken :(
Means we need a solution how to provide this defines asap.
Thorsten
--
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 8:51 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 [this message]
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=20150507085100.GA17102@suse.de \
--to=kukuk@suse.de \
--cc=libtirpc-devel@lists.sourceforge.net \
--cc=linux-nfs@vger.kernel.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).