GNU bug report logs - #62604
clarify that libtool is not MT-safe regardless of the underlying system

Previous Next

To reply to this bug, email your comments to 62604 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Barnabás Pőcze <pobrn <at> protonmail.com>
To: "bug-libtool <at> gnu.org" <bug-libtool <at> gnu.org>
Subject: clarify that libtool is not MT-safe regardless of the underlying
 system
Date: Sat, 01 Apr 2023 16:29:06 +0000

To whom it may concern,


The libtool documentation states:

  If you wish to use libltdl in a multithreaded environment, then you must
  mutex lock around libltdl calls, since they may in turn be calling
  non-thread-safe system calls on some target hosts. 
  
  (https://www.gnu.org/software/libtool/manual/libtool.html#Thread-Safety-in-libltdl)

which to me seems to imply that if the underlying system is thread-safe,
then libtool is also thread-safe. But this cannot be the case because libtool
- as far as I understand - uses a global unsychronized list for storing handles.

See https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2834 as well.


Regards,
Barnabás Pőcze

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.