From: Thorsten Kukuk <kukuk@suse.de>
To: Steve Dickson <SteveD@redhat.com>
Cc: libtirpc-devel@lists.sourceforge.net, linux-nfs@vger.kernel.org
Subject: Re: [PATCH V2] Fix Build w/gssapi disabled
Date: Sat, 9 May 2015 00:34:12 +0200 [thread overview]
Message-ID: <20150508223412.GA14634@suse.de> (raw)
In-Reply-To: <554D2A4B.6040307@RedHat.com>
On Fri, May 08, Steve Dickson wrote:
> Hello Thorsten,
>
> On 05/08/2015 04:17 AM, Thorsten Kukuk wrote:
> > On Thu, May 07, Mike Frysinger wrote:
> >
> >> it is dangerous to export raw HAVE_xxx defines -- it can break packages that
> >> use autotools themselves. they need an appropriate prefix like RPC_xxx or
> >> TIRPC_xxx.
> >
> >
> > For this and to solve the different size of the struct, I created
> > a new patch on top of current git. I only had to rearange the structs
> > a little bit, since they don't use any kerberos specific variables,
> > only standard C:
> I applied the following patch to the top of the git tree
> then I yum remove krb5-devel (which removes gssapi/gssapi.h)
>
> After an 'sh autogen.sh' and ./configure --disable-gssapi
> I'm getting the following compile errors
> http://ur1.ca/kbq67
> because gssapi.h does not exist..
>
> What am I doing wrong??
Sorry, somehow my patch was incomplete, this part did go
missing:
diff --git a/tirpc/rpc/rpcsec_gss.h b/tirpc/rpc/rpcsec_gss.h
index 217fc0d..f02de8a 100644
--- a/tirpc/rpc/rpcsec_gss.h
+++ b/tirpc/rpc/rpcsec_gss.h
@@ -35,8 +35,6 @@
#include <rpc/auth.h>
#include <rpc/clnt.h>
-#include <gssapi/gssapi.h>
-
typedef enum {
rpcsec_gss_svc_default = 0,
rpcsec_gss_svc_none = 1,
--
Thorsten Kukuk, Senior Architect SLES & Common Code Base
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany
GF: Felix Imendörffer, Jane Smithard, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg)
next prev parent reply other threads:[~2015-05-08 22:34 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
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 [this message]
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=20150508223412.GA14634@suse.de \
--to=kukuk@suse.de \
--cc=SteveD@redhat.com \
--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).