--On Friday, December 03, 2004 18:05:33 -0800 Russ Allbery <[EMAIL PROTECTED]> wrote:
> Can you tell me what version of OpenAFS this library first became > available in? All versions of openafs are able to build these libraries in archive (.a) form, but they are not built on every platform (only platforms that afs supports pthreads on. (at the very least, it is not built on netbsd 1.x or old darwin [old is < 7.0. I do not remember what macos x release that corresponds to.]) . > I've now tested the following patch and it also works and passes all of > its tests. This obviously is not the conditionalized version; I'll do > that once I have an answer to the above question. Note that I had to > include -lrx -llwp -lutil -lcom_err at the end of the link line solely to > pick up clock_haveCurrentTime; is this something that afsrpc should really > be providing? Apparently one of those other libraries wants it. This reference is a result of the use of libvolser and libbos, which are not pthread-aware. The pthread-aware libraries cannot export this interface, since pthread-rx does not use it, and because it involves unprotected access to global variables. 'we' probably should not support mixing and matching pthread and non-pthread libraries like this. It's unfortunate that I didn't polish the setcontext-based-LWP code I was working on (rt.central.org #1280) last year and try to get it into a release. setcontext and swapcontext don't have the _longjmp_unwind/__pthread_cleanup_upto craziness and would have presumably continued to work in a pthread environment
p7sExe75qImWS.p7s
Description: S/MIME cryptographic signature
