Error while compiling krb 1.5

Marcus Watts mdw at
Sat Jul 8 02:04:58 EDT 2006

Sam Hartman <hartmans at> writes:
> Well, I think I've made our position reasonably clear: we're not
> spending time on any of this but we're willing to evaluate designs and
> patches from others.
> Let me know if you would like me to better define the requirements
> I've sent out.

I agree you sent out quite a bit on requirements already.

That brings us right back around to "agreeing on semantics".  The
reason I proposed specific cases was to elicit comment and progress
here.  The different cases I proposed would all "solve" the static
library problem, with different semantics, and build consequences.
Some of those might affect MIT future plans, or others.  So far, /3/ is
easy to hate.  Your requirements express lack of faith in /2/, but that
is what pam does today.

So let me ask you this:
/1/ you say GSS mechs might be plugins.  Do you have plans or
intentions for other plugins.  Are these only on the kdc machine, or
the gss libraries, or do you expect to be making significant changes to
other parts of the library environment a vanilla k5 client
application might see?

/2/ what systems do you currently support today -- ie, when you
say "portable" - I'll bet you don't mean ebcdic or 16-bit, but do you
include aix 4.3?  sgi irix?  Do you expect everything to run everywhere
(ie, kdc on ms windows, or both static and shared libraries on aix 3.2
say?)  Also, surely you don't expect your contributors to have access
to exactly the same set of architectures?

/3/ it seems to me you've already got the complexity when you expect
initializer routines to work in plugins.  c++ constructors aren't
really part of the C language, so you got mess there.  Shared objects
are inherently hairy - even libtool won't fix that.  Somewhere here
you're going to end up trying to draw a line in the sand.  So perhaps
more importantly, how do you expect people who want to do more to

also for others,
/4/ Would other people find a libkrb5_pic.a of interest or useful?
Would --disable-servers be of use to them?  Do people actually expect
to link krb5kdc statically, and if so, what do they actually expect this
to mean for plugins?


More information about the krbdev mailing list