Error while compiling krb 1.5

Theodore Tso tytso at MIT.EDU
Mon Jul 10 00:01:18 EDT 2006

On Sun, Jul 09, 2006 at 01:27:18PM -0700, Russ Allbery wrote:
> One of the problems with any approach like this is that the threaded
> application often isn't calling com_err directly and has no idea that
> com_err actually exists.  Consider, for instance, a threaded application
> that uses GSS-API via calls through the MIT Kerberos GSS-API library.
> com_err is initialized internal to the MIT Kerberos library, which has to
> handle both threaded and non-threaded programs.  I suppose you could do
> some magic inside the MIT Kerberos library that detects whether it's
> running threaded and then calls the appropriate initialization function.

Sigh, I can imagine #ifdef'ed code which is only included in the
shared-library version of the library which calls dlopen() with a null
pointer, and searches to see if pthread_mutex_lock() is in the
progam's namespace.  I can feel my gorge rising, though...

						- Ted

More information about the krbdev mailing list