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

Previous Next

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#78321: closed (libtool fails to run ldconfig correctly on
 GNU/Linux)
Date: Fri, 16 May 2025 16:27:04 +0000

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

Your message dated Fri, 16 May 2025 19:26:25 +0300
with message-id <03069d76-10a9-40b0-ab97-46b09ee47288 <at> gmail.com>
and subject line Re: bug#78321: libtool fails to run ldconfig correctly on GNU/Linux
has caused the debbugs.gnu.org bug report #78321,
regarding libtool fails to run ldconfig correctly on GNU/Linux
to be marked as done.

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


-- 
78321: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=78321
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: libtool fails to run ldconfig correctly on GNU/Linux
Date: Thu, 8 May 2025 16:51:50 +0100

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

I'm following up on
https://lists.gnu.org/archive/html/libtool/2014-05/msg00024.html

I just ran into the same problem: a user reported they had to run
`ldconfig` manually after running `[sudo] make install` on one of my
projects (Free Recode, formerly GNU Recode). I was surprised, as I thought
the autotools ran ldconfig automatically. They do! But on GNU/Linux systems
they run `ldconfig -n`, which does not update the cache, as it implies the
-N option. This means that libraries are not found after installation.

I checked git, and this usage goes back to the initial commit. I wonder
whether something changed since then. Mostly obviously, the -n flag causes
ldconfig to process only the directories specified on the command line,
which I guess is desirable. I can't see a way to update the cache while
retaining this behaviour of -n, but maybe that doesn't make sense?

Anyway, it seems that either we should simply remove the -n flag from the
ldconfig invocation (as on BSD), or document that users will most likely
need to run ldconfig themselves after installation (which seems a shame).

-- 
https://rrt.sc3d.org

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

[Message part 5 (message/rfc822, inline)]

From: Ileana Dumitrescu <ileanadumitrescu95 <at> gmail.com>
To: 78321-done <at> debbugs.gnu.org
Cc: Bob Friesenhahn <graphicsmagick.project <at> gmail.com>,
 Reuben Thomas <rrt <at> sc3d.org>
Subject: Re: bug#78321: libtool fails to run ldconfig correctly on GNU/Linux
Date: Fri, 16 May 2025 19:26:25 +0300

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

A documentation patch has been applied to the development branch [1].

[1] 
https://git.savannah.gnu.org/cgit/libtool.git/commit/?h=development&id=ad964ee1f5382075b195313d969fb0fe6d83c8e9

-- 
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)]

Previous Next

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