From debbugs-submit-bounces@debbugs.gnu.org Sun Apr 02 00:47:40 2023 Received: (at submit) by debbugs.gnu.org; 2 Apr 2023 04:47:41 +0000 Received: from localhost ([127.0.0.1]:38825 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pipcx-0007nO-Q2 for submit@debbugs.gnu.org; Sun, 02 Apr 2023 00:47:40 -0400 Received: from lists.gnu.org ([209.51.188.17]:47938) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pie6U-0007Vi-Lw for submit@debbugs.gnu.org; Sat, 01 Apr 2023 12:29:23 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pie6U-00087U-Cr for bug-libtool@gnu.org; Sat, 01 Apr 2023 12:29:22 -0400 Received: from mail-40133.protonmail.ch ([185.70.40.133]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pie6S-0004CC-EX for bug-libtool@gnu.org; Sat, 01 Apr 2023 12:29:22 -0400 Date: Sat, 01 Apr 2023 16:29:06 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1680366556; x=1680625756; bh=3mMOg0MGwVhXz8P/Da2HxiNFLLOmmJADrQvIrQYt+4w=; h=Date:To:From:Subject:Message-ID:Feedback-ID:From:To:Cc:Date: Subject:Reply-To:Feedback-ID:Message-ID:BIMI-Selector; b=CaELZrfkykgV4KfrLX2YyWwgtrvYqIsBGObd8QHOWqJ8CegXZalw8Gh9WtWuBg60w xIdFPRIWvMRsQNjerQEUsM1FW49TOO2yD1tdRNdipOPr7aOMJBmWycVgqy2oKbh76X spHRifbko2uouibAR5zT/raVeuU/hkHnsGG4Af6/u508OOm3p+/pwsjcgAQhgz0WW9 BMg0gvcCtgteWxgsX36MWtwYOPAWhojiyZdVhmie0+y+N96Ry+CptEu+mgtXg13vir RhnnmwzbuZbrjwdlIPBDezBknnbYp9DyLWA0hj0YrSlR/cKgDpyn+EoeoHyB8/0i0G 460bd0j9iY95A== To: "bug-libtool@gnu.org" From: =?utf-8?Q?Barnab=C3=A1s_P=C5=91cze?= Subject: clarify that libtool is not MT-safe regardless of the underlying system Message-ID: Feedback-ID: 20568564:user:proton MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Received-SPF: pass client-ip=185.70.40.133; envelope-from=pobrn@protonmail.com; helo=mail-40133.protonmail.ch X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-Spam-Score: -1.3 (-) X-Debbugs-Envelope-To: submit X-Mailman-Approved-At: Sun, 02 Apr 2023 00:47:38 -0400 X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -2.3 (--) 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.=20 =20 (https://www.gnu.org/software/libtool/manual/libtool.html#Thread-Safety-i= n-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 libto= ol - as far as I understand - uses a global unsychronized list for storing han= dles. See https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2834 as well. Regards, Barnab=C3=A1s P=C5=91cze