On Sun, 28 Jan 2007, Zhe Su wrote:
Then how should I make the code thread safe? Adding mutex locks around each
libltdl call?
That should work as long as there are no other users of libltdl in the
application. If you use a 3rd party library which also uses libltdl,
then you won't be able to
* Zhe Su wrote on Sat, Jan 27, 2007 at 06:52:59PM CET:
> On 1/28/07, Ralf Wildenhues <[EMAIL PROTECTED]> wrote:
> >
> >Please note though that the CVS HEAD branch has removed the locking
> >functionality, partly because it was deemed impossible to provide a
> >useful and efficient interface, and be
Hi,
Thanks for your reply.
Regards
James Su
On 1/28/07, Ralf Wildenhues <[EMAIL PROTECTED]> wrote:
Hello James,
* Zhe Su wrote on Wed, Jan 24, 2007 at 11:51:52AM CET:
> Hi,
> I found a possible typo in libltdl in lt_dlmutex_register(). while
reading
> its source code. Patch is attached.
Th
Hello James,
* Zhe Su wrote on Wed, Jan 24, 2007 at 11:51:52AM CET:
> Hi,
> I found a possible typo in libltdl in lt_dlmutex_register(). while reading
> its source code. Patch is attached.
Thanks very much. I've applied the patch.
Please note though that the CVS HEAD branch has removed the loc
Hi,
I found a possible typo in libltdl in lt_dlmutex_register(). while reading
its source code. Patch is attached.
Regards
James Su
--- libtool-1.5.23a/libltdl/ltdl.c.old 2007-01-24 18:29:22.0 +0800
+++ libtool-1.5.23a/libltdl/ltdl.c 2007-01-24 18:46:47.0 +0800
@@ -918,7 +918,7 @
