GNU bug report logs - #40793
Documentation suggestion

Previous Next

Package: libtool;

Reported by: Reuben Thomas <rrt <at> sc3d.org>

Date: Thu, 23 Apr 2020 12:16:02 UTC

Severity: normal

Done: Ileana Dumitrescu <ileanadumitrescu95 <at> gmail.com>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Ileana Dumitrescu <ileanadumitrescu95 <at> gmail.com>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#40793: closed (Documentation suggestion)
Date: Fri, 15 Mar 2024 17:50:02 +0000
[Message part 1 (text/plain, inline)]
Your message dated Fri, 15 Mar 2024 19:48:00 +0200
with message-id <3398abaf-4792-4137-9894-a88711142981 <at> gmail.com>
and subject line Re: Documentation suggestion
has caused the debbugs.gnu.org bug report #40793,
regarding Documentation suggestion
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
40793: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=40793
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
From: Reuben Thomas <rrt <at> sc3d.org>
To: bug-libtool <at> gnu.org
Subject: Documentation suggestion
Date: Thu, 23 Apr 2020 13:15:30 +0100
[Message part 3 (text/plain, inline)]
libtool.texi contains the following:

"It was reported that GNU/Linux's glibc 2.0's 'dlopen' with 'RTLD_LAZY'
(that libltdl uses by default) is not thread-safe, but this problem is
supposed to be fixed in glibc 2.1.  On the other hand, 'RTLD_NOW' was
reported to introduce problems in multi-threaded applications on FreeBSD."

I suggest removing this material: glibc 2.1 was released over 20 years ago.
I have looked through both the glibc changelogs and git history to try to
ascertain whether in fact this bug was mentioned as being fixed, but I can
find nothing relevant. The same applies to the FreeBSD case.

Evidence on the positive side is that dlopen(3) states explicitly that the
function is thread safe, and POSIX defines it as such. Therefore it might
be reasonable to state that modern dlopen implementations should be threads
safe. Or it might not. (Does someone know more about this?) In the latter
case, the rest of the paragraph could be left as-is, which is to say,
reasonably conservative.

-- 
https://rrt.sc3d.org
[Message part 4 (text/html, inline)]
[Message part 5 (message/rfc822, inline)]
From: Ileana Dumitrescu <ileanadumitrescu95 <at> gmail.com>
To: 40793-done <at> debbugs.gnu.org
Subject: Re: Documentation suggestion
Date: Fri, 15 Mar 2024 19:48:00 +0200
[Message part 6 (text/plain, inline)]
Thank you for your bug report! I have removed the warnings about
thread safety with 'dlopen' in libtool's documentation.

-- 
Ileana Dumitrescu

GPG Public Key: FA26 CA78 4BE1 8892 7F22 B99F 6570 EA01 146F 7354
[OpenPGP_0x6570EA01146F7354.asc (application/pgp-keys, attachment)]
[OpenPGP_signature.asc (application/pgp-signature, attachment)]

This bug report was last modified 1 year and 65 days ago.

Previous Next


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