librpcsecgss has a broken config script but valid GSSAPI_CFLAGS and GSSAPI_LIBS variables. krb5-config or krb4-config should be used to force configure to do the right thing. Reproducible: Always Steps to Reproduce:
Created attachment 125806 [details] librpcsecgss-0.14-r1.ebuild This ebuild builds librpcsecgss correctly on systems with krb5 installed into any location. However, it forces the use of krb5-config; a test for the binary's existence would be better.
can you be a little more verbose as to the problem ? librpcsecgss does a pkg-config check for gssapi.pc which mit-krb5 should be providing ... -config scripts are dead, pkg-config + *.pc files are the way to go
(In reply to comment #2) > can you be a little more verbose as to the problem ? librpcsecgss does a > pkg-config check for gssapi.pc which mit-krb5 should be providing ... -config > scripts are dead, pkg-config + *.pc files are the way to go > Never mind, I was using a stale shell with old PKG_CONFIG_PATH and assumed that the m4s in this lib were at fault for it not finding libgssapi. Sorry for the trouble :-/.
Created attachment 125910 [details, diff] librpcsecgss-0.14-r1.diff I knew I wasn't just being stupid! This ebuild no longer depends on libgssapi. It builds against Heimdal Kerberos. Heimdal currently doesn't use pkg-config, but I'm talking with Love (its author) to see if it could provide a .pc file to replace libgssapi's.
Reopening - please do take a look, as with this we can mark libgssapi and Heimdal as conflicts and close a number of bugs.
that is not the direction things should be going. fix heimdal to work like mit-krb5 or dont bother. see Bug 134064 where heimdal is already not a viable option as a replacement for mit-krb5
(In reply to comment #6) > that is not the direction things should be going. fix heimdal to work like > mit-krb5 or dont bother. > > see Bug 134064 where heimdal is already not a viable option as a replacement > for mit-krb5 > Not to flame, but I really think it should be "fix mit-krb5 to work like Heimdal". MIT Kerberos requires an extra intermediary library which Heimdal does not. I've got nfs-utils built without libgssapi - in the bug you mentioned. Heimdal has always been ahead of MIT Kerberos in features - they implemented replay caching, PKINIT, LDAP backends, etc first, and even now there are still features MIT krb5 doesn't have, like the ability to produce AFS keyfiles. So saying "make Heimdal work like MIT" isn't exactly a solution. It already works better, it's just that nfs-utils is hardcoded to use a particular GSS library which it doesn't need to.
i'm talking about pkg-config scripts. i do not want to ever add logic to calling some ugly *-config script for flags. get heimdal to install a proper .pc file.
Already done, around an hour ago. ---------- Forwarded message ---------- From: lha@it.su.se To: heimdal-source-changes@h5l.se Date: Tue, 24 Jul 2007 23:21:20 +0200 Subject: [Heimdal-source-changes] heimdal r21691 - trunk/heimdal/tools Author: lha Name: Love Hörnquist Åstrand Date: 2007-07-24 23:21:19 +0200 (Tue, 24 Jul 2007) Repository: heimdal Repository Path:/afs/su.se/services/svn/heimdal New Revision: 21691 Added: trunk/heimdal/tools/heimdal-gssapi.pc.in Log: pkg-config file for libgssapi in heimdal.
Created attachment 126186 [details, diff] librpcsecgss-0.14-r1-heimdal_pkg-config.ebuild.diff Just changing the dependency to allow app-crypt/heimdal without app-crypt/libgssapi -- the rest is accounted for by the libgssapi.pc file, if created by the heimdal ebuild (see Bug #185899).
I think this is no longer relevant since it uses libgssglue rather than libgssapi, and that you can simply switch at runtime (sigh, even though I don't like that approach at all).
