bug#78321: libtool fails to run ldconfig correctly on GNU/Linux

--000000000000b446d2063502e089
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

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.

Bob

On Tue, May 13, 2025, 4:12=E2=80=AFAM Reuben Thomas via bug-libtool via Bug=
 reports
for the GNU libtool shared library maintenance tool <[email protected]>
wrote:

> On Mon, 12 May 2025 at 20:08, Ileana Dumitrescu <
> [email protected]> wrote:
> Thanks for the quick reply!
>
>
>> This was also previously reported in bug#30402 [1]
>
>
> By me!
>
> Updating the shared library cache from scratch by executing ldconfig in
>> libtool could cause a lot of headache for developers,
>
>
> It would be good to briefly say why it's a problem. (I don't know, and
> Debian seems to run ldconfig whenever I install or uninstall a shared
> library, so it doesn't seem a big deal at least there.)
>
> The following could be added:
>>
>> """
>> After a 'make install' for many GNU/Linux systems, 'ldconfig LIBDIR' may
>> need to be executed to help locate newly installed libraries, but you
>> should consult with a system administrator before updating the shared
>> library cache as this should be done with great care and consideration.
>> """
>>
>
> Again, it would be good if possible to briefly outline potential problems=
.
> Then the informational message is pretty much complete: it will
>
>    - 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
>
> --
> https://rrt.sc3d.org
>

--000000000000b446d2063502e089
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">Libtool works on many different operating systems, which =
behave in various ways. Some OSs will find a new library automatically if i=
t is installed in the existing configured library paths.<div dir=3D"auto"><=
br></div><div dir=3D"auto">The library installed might not ever be intended=
 to be used by the currently executing OS because it is part of new distrib=
ution builds.</div><div dir=3D"auto"><br></div><div dir=3D"auto">Sometimes =
libraries are installed privately, using hard-coded run-paths in the depend=
ent binaries. This is very common when a different version of the software =
is to be run than the OS is designed to support.</div><div dir=3D"auto"><br=
></div><div dir=3D"auto">Expecting a libtool (merely a shell script!) maint=
ainer to write such a document is unreasonable. It is possible that GNU has=
 such a document specific to GNU systems.</div><div dir=3D"auto"><br></div>=
<div dir=3D"auto">Bob</div></div><br><div class=3D"gmail_quote gmail_quote_=
container"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, May 13, 2025, 4:12=
=E2=80=AFAM Reuben Thomas via bug-libtool via Bug reports for the GNU libto=
ol shared library maintenance tool &lt;<a href=3D"mailto:[email protected]=
g">[email protected]</a>&gt; wrote:<br></div><blockquote class=3D"gmail_q=
uote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1e=
x"><div dir=3D"ltr"><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gm=
ail_attr">On Mon, 12 May 2025 at 20:08, Ileana Dumitrescu &lt;<a href=3D"ma=
ilto:[email protected]" target=3D"_blank" rel=3D"noreferrer">ile=
[email protected]</a>&gt; wrote:</div><div dir=3D"ltr" class=3D"gma=
il_attr"><div style=3D"font-family:arial,helvetica,sans-serif;font-size:sma=
ll" class=3D"gmail_default"><div>Thanks for the quick reply!<br></div></div=
></div><div dir=3D"ltr" class=3D"gmail_attr"><br></div><blockquote class=3D=
"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(2=
04,204,204);padding-left:1ex"><br>
This was also previously reported in bug#30402 [1]</blockquote><div><br></d=
iv><div style=3D"font-family:arial,helvetica,sans-serif;font-size:small" cl=
ass=3D"gmail_default">By me!</div><div style=3D"font-family:arial,helvetica=
,sans-serif;font-size:small" class=3D"gmail_default"><br></div><blockquote =
class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px sol=
id rgb(204,204,204);padding-left:1ex">
Updating the shared library cache from scratch by executing ldconfig in<br>
libtool could cause a lot of headache for developers,</blockquote><div><br>=
</div><div><div style=3D"font-family:arial,helvetica,sans-serif;font-size:s=
mall" class=3D"gmail_default">It would be good to briefly say why it&#39;s =
a problem. (I don&#39;t know, and Debian seems to run ldconfig whenever I i=
nstall or uninstall a shared library, so it doesn&#39;t seem a big deal at =
least there.)<br></div><br></div><blockquote class=3D"gmail_quote" style=3D=
"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-le=
ft:1ex">The following could be added:<br>
<br>
&quot;&quot;&quot;<br>
After a &#39;make install&#39; for many GNU/Linux systems, &#39;ldconfig LI=
BDIR&#39; may<br>
need to be executed to help locate newly installed libraries, but you<br>
should consult with a system administrator before updating the shared<br>
library cache as this should be done with great care and consideration.<br>
&quot;&quot;&quot;<br></blockquote><div><br></div><div><div style=3D"font-f=
amily:arial,helvetica,sans-serif;font-size:small" class=3D"gmail_default">A=
gain, it would be good if possible to briefly outline potential problems. T=
hen the informational message is pretty much complete: it will<br></div><di=
v style=3D"font-family:arial,helvetica,sans-serif;font-size:small" class=3D=
"gmail_default"><ul><li>explains that users may now need to run ldconfig</l=
i><li>gives them the command to run</li><li><i>says why this might not be a=
 good idea <b>(this bit currently missing!)<br></b></i></li><li>explains wh=
at won&#39;t work until the command is run</li></ul></div></div></div><span=
 class=3D"gmail_signature_prefix">-- </span><br><div dir=3D"ltr" class=3D"g=
mail_signature"><div dir=3D"ltr"><div><div dir=3D"ltr"><a href=3D"https://r=
rt.sc3d.org" target=3D"_blank" rel=3D"noreferrer">https://rrt.sc3d.org</a><=
/div></div></div></div></div>
</blockquote></div>

--000000000000b446d2063502e089--