I'm running a non-pthreads version of perl, and so I'm getting
an error when xerces attempts to call the mutex_lock.
Would it be possible to make the perl module Xerces.so statically
linked against pthreads if the perl install isn't? Would this work?
Or could it check at runtime and dynamically load pthreads?
Or as a rather ick last resource, if you're compiling it for
a non threaded perl could you just add in a mutex_lock dummy functions
(and for any other that xerces-c uses). I believe (hand not on heart)
that xerces is only using these to be thread safe, and an unthreaded
perl will be pretty damn thread safe.
It took me a while to figure out what's going on, so it's possible that
this is causing trouble for other people too.
(or maybe I've just missed a vital config option <grin>)
--
Christopher Gutteridge -- [EMAIL PROTECTED] -- +44 (0)23 8059 4833
Now Playing: "Private goes public" from 99.9F0 - Suzanne Vega
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
