krb5 libraries and circular dependencies

Jeffrey Hutzelman jhutz at
Thu Jun 3 04:13:29 EDT 2010

--On Tuesday, June 01, 2010 12:30:06 PM -0700 "Henry B. Hotz" 
<hotz at> wrote:

> On May 29, 2010, at 9:03 AM, krbdev-request at wrote:
>> On Fri, 28 May 2010 15:32:07 -0400
>> Sam Hartman <hartmans at MIT.EDU> wrote:
>>> If the krb5 build system didn't use rpath, I think it would be fairly
>>> unlikely that a plugin would get a different libkrb5 than the
>>> application.  However, since rpath is used, I guess it is reasonably
>>> easy to have this happen.
>> In some distributions rPath is forbidden exactly for these reasons, and
>> needs an exception to be granted in order to be allowed for any single
>> package.
> My own experience has been that if you *don't* use rpath (or something
> similar) then it's "fairly unlikely" that libkrb5 will find *any*
> plugins.  That's doing custom builds, not OS integration of course.

Presumably this is because your plugins are built against libraries that 
are not in the system default library search path.  The solution is to do 
your custom builds "correctly", for whatever value of "correctly" makes it 
work. :-)

More information about the krbdev mailing list