Why weak referencing pthread_equal() in k5-thread.h?

KAMADA Ken'ichi kamada at nanohz.org
Tue Apr 12 20:01:55 EDT 2005

At Tue, 12 Apr 2005 01:33:18 -0400,
Ken Raeburn <raeburn at MIT.EDU> wrote:
> > Why pthread_*() other than pthread_once() and
> > pthread_mutexattr_setrobust_np() are weakly referenced in k5-thread.h?
> > I see pthread_once() and pthread_mutexattr_setrobust_np() are used to
> > check whether the libpthread is loaded in the K5_PTHREAD_LOADED macro,
> > but I don't see why other functions need to be weakly referenced.
> Different systems have different sets of stubs.  To make things worse, 
> some systems have stubs that just don't work.

I see, thanks.  There may be some systems which have the pthread
support but no libc stubs.

> > Background:
> >
> > MIT krb5-1.4 (and current on Apr 6) doesn't work on NetBSD
> > (unless the calling program is linked with libpthread).
> Okay, that's a bug...  Odd that we didn't catch it, we do some test 
> builds on NetBSD.  Oh, but we tend to expect the runtime tests to fail 
> on NetBSD, because of some RPC issues, so we might not have noticed if 
> the failure happened earlier in the run.
> I'll try to fix this up.  I don't know if it'll get into the 1.4.1 
> release coming soon, though.

Thank you a lot.  With pthread_equal() worked-around, krb5-1.4
(at least the small set of functions I'm using) seems to be working.

KAMADA Ken'ichi <kamada at nanohz.org>

More information about the krbdev mailing list