bug#40793: Documentation suggestion
Reuben Thomas via Bug-libtool via Bug reports for the GNU libtool shared library maintenance tool <[email protected]>
| Newsgroups | gmane.comp.gnu.libtool.bugs |
|---|---|
| Message-ID | <CAOnWdojqo_sKiaXoS0ZQ585_CD9MuQRLYUbHfTSgsH-1MpPUOg@mail.gmail.com> |
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 _______________________________________________ Bug-libtool mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-libtool