On Oct 19, 2:29 pm, Ken Raeburn <raeb...@mit.edu> wrote: > > Okay, it looks like it's never even calling krb5int_pthread_loaded, > which should mean that it's always following the code path (in > selecting macro definitions) that assumes the thread support is always > linked in. This would be dependent on some configuration macros, > HAVE_PRAGMA_WEAK_REF and NO_WEAK_PTHREADS; can you see which are set > in include/autoconf.h in the build tree? The former should be defined > (based on tests of the compiler, so it may also depend on which > compiler you're using), and the latter should not (selected in the > configure script based on the OS version). > > Ken
Both are set to 1. [r...@localhost]/local/BuildArea/krb5/krb5-1.7/src#grep HAVE_PRAGMA_WEAK_REF include/autoconf.h #define HAVE_PRAGMA_WEAK_REF 1 [r...@localhost]/local/BuildArea/krb5/krb5-1.7/src#grep NO_WEAK_PTHREADS include/autoconf.h #define NO_WEAK_PTHREADS 1 I am using an old version of gcc (3.2.3) ________________________________________________ Kerberos mailing list Kerberos@mit.edu https://mailman.mit.edu/mailman/listinfo/kerberos
