I've seen similar error on HPUX also - some versions of libc (on HPUX) has dependency on TLS (thread local storage) symbols - which requires that you link specifically with lpthread.. This is done mainly for performance reasons.. I suspect something similar to be happening on Solaris too - just a thought.
-Madhu -----Original Message----- From: Jeff Trawick [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 31, 2002 3:12 PM To: Dale Ghent Cc: [EMAIL PROTECTED] Subject: Re: 1.3 weirdness with AcceptMutex on Solaris Dale Ghent <[EMAIL PROTECTED]> writes: > | > Yeah, I see that, too. I have to add '-lthread -lpthread' to the > | > src/Makefile manually. What is the actual symptom you see if you don't do that? > "All calls to libthread and libpthread are no-ops if the application does > not link -lthread or -lpthread. The runtime library libc has many > predefined libthread and libpthread stubs that are null procedures. True > procedures are interposed by libthread or libpthread when the application > links both libc and the thread library." If a plug-in uses threads and httpd is bound (?) to some dummy thread routines in libc, doesn't that screw up the plug-in or confuse libpthread? Emperical results show that as long as httpd doesn't bind to dummy thread routines in libc the plug-in's use of threads is fine. See my separate post a few minutes ago... Thanks!!! -- Jeff Trawick | [EMAIL PROTECTED] | PGP public key at web site: http://www.geocities.com/SiliconValley/Park/9289/ Born in Roswell... married an alien...
