From b45d9518aebfcd64e8359b9dce99067b00a33841 Mon Sep 17 00:00:00 2001 From: Ken Raeburn Date: Tue, 16 May 2006 02:56:59 +0000 Subject: Don't look for pthread_mutexattr_setrobust_np Apparently Red Hat's Fedora Core 5 defines it but doesn't declare it, so we'd have to declare it before testing the address. While it was once useful for checking whether the pthread code had been loaded, I think the other tests done now are more effective and this isn't needed any more. git-svn-id: svn://anonsvn.mit.edu/krb5/trunk@18012 dc483132-0cff-0310-8789-dd5450dbe970 --- src/util/support/threads.c | 5 ----- 1 file changed, 5 deletions(-) (limited to 'src/util') diff --git a/src/util/support/threads.c b/src/util/support/threads.c index 1ac9c6150..ebc1dafae 100644 --- a/src/util/support/threads.c +++ b/src/util/support/threads.c @@ -144,11 +144,6 @@ int krb5int_pthread_loaded (void) || &pthread_mutex_init == 0 || &pthread_self == 0 || &pthread_equal == 0 - /* This catches Solaris 9. May be redundant with the above - tests now. */ -# ifdef HAVE_PTHREAD_MUTEXATTR_SETROBUST_NP_IN_THREAD_LIB - || &pthread_mutexattr_setrobust_np == 0 -# endif /* Any program that's really multithreaded will have to be able to create threads. */ || &pthread_create == 0 -- cgit