GNU bug report logs - #78321
libtool fails to run ldconfig correctly on GNU/Linux

Previous Next

Full log

Message #11 received at 78321 <at> debbugs.gnu.org (full text, mbox):

From: Reuben Thomas <rrt <at> sc3d.org>
To: Ileana Dumitrescu <ileanadumitrescu95 <at> gmail.com>
Cc: 78321 <at> debbugs.gnu.org
Subject: Re: bug#78321: libtool fails to run ldconfig correctly on GNU/Linux
Date: Tue, 13 May 2025 10:11:27 +0100

[Message part 1 (text/plain, inline)]

On Mon, 12 May 2025 at 20:08, Ileana Dumitrescu <
ileanadumitrescu95 <at> gmail.com> 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

[Message part 2 (text/html, inline)]

Previous Next

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