On 13/05/2025 18:18, Ileana Dumitrescu wrote: > On 13/05/2025 14:38, Bob Friesenhahn wrote: >> Libtool works on many different operating systems, which behave in >> various ways. Some OSs will find a new library automatically if it is >> installed in the existing configured library paths. >> >> The library installed might not ever be intended to be used by the >> currently executing OS because it is part of new distribution builds. >> >> Sometimes libraries are installed privately, using hard-coded run- >> paths in the dependent binaries. This is very common when a different >> version of the software is to be run than the OS is designed to support. >> >> Expecting a libtool (merely a shell script!) maintainer to write such >> a document is unreasonable. It is possible that GNU has such a >> document specific to GNU systems. > > Thank you for your explanation. I think this can be described briefly in > notes.texi to list some of what you outlined above. > >> On Tue, May 13, 2025, 4:12 AM Reuben Thomas via bug-libtool via Bug >> reports for the GNU libtool shared library maintenance tool > libtool@gnu.org > wrote: >>       * explains that users may now need to run ldconfig >>       * gives them the command to run >>       * /says why this might not be a good idea *(this bit currently >>         missing!) >>         */ >>       * explains what won't work until the command is run > > Since libtool is designed to be portable and with the variability for > each system and user needs, I will not add the informational message > to the finishing mode. However, I will add an incomplete list of > issues to libtool's documentation. I have attached a proposed patch for review. I made minor changes to the explanation Bob provided, but it is largely the same. -- Ileana Dumitrescu GPG Public Key: FA26 CA78 4BE1 8892 7F22 B99F 6570 EA01 146F 7354